cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node
Date Wed, 30 Aug 2017 22:11:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148129#comment-16148129
] 

Blake Eggleston commented on CASSANDRA-5901:
--------------------------------------------

Before getting into the implementation details, there are some things with the configuration
approach I’m not sure about.

First, I think using consistency levels as configuration options for this might be overkill.
Mainly because there’s so many of them, and most of them don’t make any sense for bootstrap
(ie: what do you do when someone puts in LOCAL_SERIAL). Something simple like {{bootstrap_consistency:
none/global/dc_local}} leaves less room for confusion on the operator side, and less input
validation on the implementation side. The only use case I can see not being served by those
options would be if you wanted to do dc_local with the data coming from another datacenter.

Second, do you think per-keyspace settings are necessary? It seems unlikely that you’d want
different settings for each keyspace. If so, do you think it would be better to put them on
the schema or something? Having them in the config is going to make validation difficult.
We won’t know if there are typos in a keyspace name until after the node has joined the
ring, and it’s too late.

> 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


Mime
View raw message