Queue processor handle shard ownership lost #3553
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yycptt
approved these changes
Nov 3, 2022
wxing1292
approved these changes
Nov 3, 2022
wxing1292
pushed a commit
that referenced
this pull request
Nov 3, 2022
* Not retry shard ownership lost
wxing1292
pushed a commit
that referenced
this pull request
Nov 3, 2022
* Not retry shard ownership lost
alexshtin
pushed a commit
that referenced
this pull request
Nov 15, 2022
* Not retry shard ownership lost
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Queue processor handle shard ownership lost
Why?
There is a case that the processor could receive shard ownership lost error but the shard continues to run. In this case, the task processing gets blocked
How did you test it?
Potential risks
Is hotfix candidate?