Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change Blobs.CentralizedPoisonQueue default (#1106) #2794

Merged
merged 1 commit into from
May 4, 2018
Merged

Conversation

mathewc
Copy link
Member

@mathewc mathewc commented May 4, 2018

Addresses #1106. With this change, poison messages for blobs will be co-located in the storage account of the source blob container.

When I fixed this in core SDK, we couldn't take the breaking change for v1, hence this switch default.

@mathewc mathewc requested a review from brettsam May 4, 2018 17:39
Copy link
Member

@brettsam brettsam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have any docs that talk about this that we'll need to update? I don't think we get that detailed anywhere, but just wanted to double-check.

@mathewc
Copy link
Member Author

mathewc commented May 4, 2018

I don't think we detail this really. Now all poison queue handling will be consistent for both queues and blobs. However, the user expectation is generally that it behaves like this, which is what was addressed in the original core SDK fix Azure/azure-webjobs-sdk#804.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants