Check KV ready before starting nextgenrepl #23
Merged
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
If riak_kv is not ready, and riak_kv_replrtq_snk starts work it will fetch from queues on the remote cluster, but not be able to put those changes into this cluster. This defers the prompting of work on startup until after riak_kv is ready. The `riak_kv_replrtq_peer` can also prompt work - so this too is delayed until riak_kv has started. The riak_kv_ttaaefs_manager will not function correctly without riak_kv being started, so this also has startup deferred should riak_kv not be ready after the initial startup timeout.
stephenwood24-nhs
approved these changes
Mar 6, 2024
Allows for timeout to be reduced in test and aligned with waits in test.
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.
If riak_kv is not ready, and
riak_kv_replrtq_snkstarts work it will fetch from queues on the remote cluster, but not be able to put those changes into this cluster.This defers the prompting of work on startup until after riak_kv is ready. The
riak_kv_replrtq_peercan also prompt work - so this too is delayed until riak_kv has started.The
riak_kv_ttaaefs_managerwill not function correctly without riak_kv being started, so this also has startup deferred should riak_kv not be ready after the initial startup timeout.