HIVE-24450: DbNotificationListener Request Notification IDs in Batches #1718
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
|
@belugabehr Although I am not very familiar with this area, but what happens if multiple HMS are running in HA? Wouldn't this solution mean, that potentially the order of the notification events will change? Two HMS are running HMS 1 gets id range 1-10, HMS 2 gets 11-20. Then openTxn notification goes to HMS 2 and allocateWriteId notification goes to HMS1. The sequence of the ids will not represent the sequence of the events. Wouldn't this mess up acid table replication? |
|
In HA case how will the ordering of events be maintained? Acid Replication relies on the event sequence. So the ordering needs to be maintained. |
|
Thank you all for the feedback. Please review my notes: |
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 changes were proposed in this pull request?
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?