Update pgcopydb sentinel's replay_lsn asynchronously. #267 8000
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
When in follow replay mode, the pgcopydb sentinel is updated quite frequently so that we can see progress being made and be reactive about when to implement the migration cutover. Now, we might have to consider some latency with the source database system where the replay_lsn is published, so rate-limiting those sentinel updates is important. Also, rate limiting alone might not be enough to prevent slowing down the replay process, so switch to using libpq async API.
cf4baf1 to
e6a2266
Compare
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.
When in follow replay mode, the pgcopydb sentinel is updated quite frequently so that we can see progress being made and be reactive about when to implement the migration cutover.
Now, we might have to consider some latency with the source database system where the replay_lsn is published, so rate-limiting those sentinel updates is important. Also, rate limiting alone might not be enough to prevent slowing down the replay process, so switch to using libpq async API.
See #254