lib/model, lib/protocol: Sequence ClusterConfig properly (fixes #3448) #3452
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
|
@st-jenkins retest this please |
calmh
changed the title
|
@st-review merge |
st-review
pushed a commit
that referenced
this pull request
Jul 27, 2016
|
I can't think of a reason this is needed. |
st-review
added
the
frozen-due-to-age
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.
Purpose
Fix it...
Testing
I'm running some integration stuff, but I'm not 100% sure of this one. There ought to have been a good reason for the async call to ClusterConfig, typically to avoid mutex deadlocks. But I can't remember directly. Help me think this through?