Allow NewMember hook before initialialization#37
Merged
Conversation
…zation Signed-off-by: Max Asnaashari <max.asnaashari@canonical.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
After we are initialized, we send out a message to every other cluster member, telling them to run the
NewMemberhook. However, if those cluster members are also in the process of initializing, then this will fail and our cluster member won't initialize properly.This allows
POSTandGETon/clusterto be available pre-init. In the case ofPOST, which is used for the above example, we will allow the request to go through it it's a cluster notification to run the hook. Otherwise, both methods will fail if the daemon has not been initialized, as before.