Backup and DR would not share mutations if started on different versions of FDB #2202
Conversation
|
I'm confused at what this PR tries to achieve without diving into the code detail. Does this PR solve the statement in the title "Backup and DR would not share mutations if started on different versions of FDB" or achieve that statement? |
|
The title is describing the current situation, which is undesirable. This PR changes it so that the mutation log is shared correctly. |
…ure-share-mutations
Co-Authored-By: A.J. Beamon <[email protected]>
Co-Authored-By: A.J. Beamon <[email protected]>
duplicate mutation stream did not work properly when multiple ranges exist with the same begin key
|
It is possible backup will need be started and aborted multiple times to get backup and DR to share, because the destUIDLookup could actually have ranges from more than 2 versions of FDB (although it would only be saving the mutations for two of those lookup entries). When backup is started it will randomly join with one of the lookups for the same range, and if that happens to be the active DR then it will just work. If it is not the DR one, when you abort the backup it will remove the lookup key associated with the backup, so the next time backup starts it will join with a different lookup. |
3 participants
No description provided.