Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added riak_test for new participation_in_coverage option. #1300

Merged

Conversation

russelldb
Copy link
Member

Test for basho/riak_core#917 (and basho/riak_kv#1664)

First test cluster of 5 nodes, setting one to node 5 to no coverage
Then check:
participation_in_coverage environment variable is set correctly
participation_in_coverage metadata is set correctly on ring
generated coverage plans do not include node 5.
Set node 5 back to coverage and check:
participation_in_coverage metadata is set correctly on ring
generated coverage plans do re-include node 5.

First test cluster of 5 nodes, setting one to node 5 to no coverage
Then check:
  participation_in_coverage environment variable is set correctly
  participation_in_coverage metadata is set correctly on ring
  generated coverage plans do not include node 5.
Set node 5 back to coverage and check:
  participation_in_coverage metadata is set correctly on ring
  generated coverage plans do re-include node 5.
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIce simple example of how to test riak_kv features. You should have blogged this one.

@martinsumner
Copy link

Test was added into develop-2.9 and develop-3.0. Has since been updated to try and handle some unpredictability resulting from the choice of small ring size. This puts the original test back into 2.2.5 for completeness - which is OK.

@martinsumner martinsumner merged commit 378089e into basho:develop-2.2.5 Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants