HIVE-28772: Clear REPL_TXN_MAP table on DR when deleting replication policy #5656
+135
−0
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
…policy Details: Problem : * Suppose user is doing incremental replication. As per current design it can happen that a transaction can span across replication cycles. * So, if open transaction gets replayed to DR side and a user deletes the databases and policy on both Src and DR side then there will be dangling entry in REPL_TXN_MAP table on the DR side. * If a user creates the database name with the same name as previous then after 11 days housekeeper thread deletes the REPL_TXN_MAP dangling entry which basically sets the database incompatible in the newly created database from new replication policy. Solution : * while deleting REPL LOAD scheduled query, it will check for Repl Created Transactions on DR side and if there is any then it will abort it and put the flag repl.Incompatible on DR side which indicates the transaction was aborted so bootstrap will be required for future replication. * By any means if user try to resume the replication then DR will be in inconsistent state. * if there are no Repl created open transactions then it will be the same operation as current
|
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.
Details:
Problem :
Solution :
What changes were proposed in this pull request?
Why are the changes needed?
Does this PR introduce any user-facing change?
Is the change a dependency upgrade?
How was this patch tested?