Verify Riak Startup when Strong Consistency is Misconfigured #636
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
AAE is disabled. (defect basho/riak_kv#959) - Adds additional console output to reset-current-env to explain configuration and steps being executed - Adds the -n option to the reset-current-env script to specify the number of nodes to build. By default, 5 will be created.
|
Looks good and test passes. 👍 |
jburwell
added a commit
that referenced
this pull request
Jun 16, 2014
Verify Riak Startup when Strong Consistency is Misconfigured
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.
Tests the Riak startup behavior when strong consistency is enabled and AAE is disabled as described in basho/riak_kv#959. Riak should startup without error, but the ensembles should never reach quorum.
In addition to adding this test case, the following enhancements were made to the
reset-current-env.shscript to properly execute strong consistency tests requiring more than five (5) nodes:I had intended to add a test to verify the Riak KV warning PR. Unfortunately, riak_test's log capture facility is not enabled at startup, and requires significant changes to allow such operation. @kelly and I determined that these changes were too invasive given the proximity of the Riak 2.0 release. Therefore, I have opened the following tickets to enhance the framework and add the automated test for the warning to be addressed in the 2.1 release cycle: