Nhse o34 orc.i14 startup #11
Open
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
Make the default number of vnode to start per management tick higher. Still start them in series, but prefer those not owned in the current ring - and so less likely to contain data. This makes it more likely that the `maybe_ring_changed/4` function will start the active vnodes in parallel as expected.
Do we need to know about vnode pools starting - but not vnodes?
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.
See #8
This changes the riak_core_vnode update_never_started so that it prefers to start vnodes that are not owned by this node within the ring. These vnodes will start in series - so this makes it more likely that vnodes owned (and containing data) will start in parallel.
Changes logging so that we log the starting of the vnode, not of the vnode worker pool.