You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2017/06/29 06:55:00 UTC
[jira] [Comment Edited] (CASSANDRA-5901) Bootstrap should also make
the data consistent on the new node
[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067855#comment-16067855 ]
Marcus Eriksson edited comment on CASSANDRA-5901 at 6/29/17 6:54 AM:
---------------------------------------------------------------------
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/rebuild {{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?). The supported consistency levels are {{ANY}}, {{QUORUM}}, {{LOCAL_QUORUM}}, {{TWO}}.
a few dtests:
https://github.com/krummas/cassandra-dtest/commits/marcuse/5901
was (Author: krummas):
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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org