cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node
Date Fri, 03 Aug 2018 12:06:00 GMT


Marcus Eriksson commented on CASSANDRA-5901:

So finally got back to this, pushed an updated version here:

Regarding configuration, I changed it to be {{none/dc_local/global}}, and they map to {{ANY/LOCAL_QUORUM/QUORUM}}.
{{ConsistencyLevel}} is still used internally for {{blockFor}} calculations etc. 

I also kept the possibility to override for specific keyspaces if some user wants to enable
this on a per-keyspace basis.

It disables consistent bootstrap for RF = 2 since we either bootstrap with all replicas up
and then we end up consistent (CASSANDRA-2434) or we bootstrap with a node down and then we
can only stream from a single replica anyway and can't get a consistent bootstrap.


> Bootstrap should also make the data consistent on the new node
> --------------------------------------------------------------
>                 Key: CASSANDRA-5901
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message