[
https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-5901:
---------------------------------------
Status: Patch Available (was: Reopened)
https://github.com/krummas/cassandra/commits/marcuse/5901
Adds new config parameters to the yaml:
{code}
default_bootstrap_consistency_level: ANY
bootstrap_consistency_level:
keyspace1: QUORUM
{code}
This means that on bootstrap/replace {{keyspace1}} will stream the repaired
data from a single node and the unrepaired data from a {{QUORUM}} of the nodes,
all other keyspaces will stream like today (that is what the {{ANY}}
represents, maybe using {{ONE}} for this makes more sense?)
a few dtests:
https://github.com/krummas/cassandra-dtest/commits/marcuse/5901
> Bootstrap should also make the data consistent on the new node
> --------------------------------------------------------------
>
> Key: CASSANDRA-5901
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5901
> Project: Cassandra
> Issue Type: Improvement
> Reporter: sankalp kohli
> Assignee: Marcus Eriksson
> Priority: Minor
> Fix For: 4.x
>
>
> Currently when we are bootstrapping a new node, it might bootstrap from a
> node which does not have most upto date data. Because of this, we need to run
> a repair after that.
> Most people will always run the repair so it would help if we can provide a
> parameter to bootstrap to run the repair once the bootstrap has finished.
> It can also stop the node from responding to reads till repair has finished.
> This could be another param as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
