Handling NO Coordinator Scenario and Data Loss in the current Design #11298
+151
−41
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.
This PR combines the issues I have already handled by these two PRs:
With this PR, I have made few changes to handle both the issues in more robust, resilient and performant ways.
I have another design change proposal with this PR which handles much more scenarios without doing any OffsetSync or other efforts in much more resilient ways.
The explanantion and the pictorial view of the issues ca be found in this Design change proposal doc which is proposing the changes made by this PR