This repository was archived by the owner on Feb 18, 2025. It is now read-only.
Expose Binlog Coordinates at time of promotion as Environment Variable #1323
Conversation
This file contains hidden or 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
|
I verified that the binlog coordinates can be accessed via the post failover processes. |
shlomi-noach
suggested changes
Mar 5, 2021
35f4f45 to
48c7ace
Compare
shlomi-noach
approved these changes
Mar 7, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Related issue: #1322
Description
This PR exposes the binlog coordinates available in promotedReplica.SelfBinlogCoordinates during recovery as environment variable available for the PostFailoverProcesses.
Environment Variable Name: ORC_SUCCESSOR_BINLOG_COORDINATES
Corresponding Magic Token: {successorBinlogCoordinates}