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

Better Handling for enable_consensus [JIRA: TOOLS-255] #90

Open
pogzie opened this issue Mar 29, 2016 · 0 comments
Open

Better Handling for enable_consensus [JIRA: TOOLS-255] #90

pogzie opened this issue Mar 29, 2016 · 0 comments

Comments

@pogzie
Copy link

pogzie commented Mar 29, 2016

As commented by Kaz in ticket 13306

"Riaknostic verifies the combination of AAE and strong consistency, and expects enable_consensus is always defined as true or false in riak_core section of app.config. If a user uses riak.conf, enable_consensus is generated by cuttlefish. However, a user used app.config which didn't contain enable_consensus config."

A workaround is to use riak.conf, or add the following in riak_core section of app.config:
{enable_consensus, false}

@Basho-JIRA Basho-JIRA changed the title Better Handling for enable_consensus Better Handling for enable_consensus [JIRA: TOOLS-255] Mar 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants