[
https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149327#comment-16149327
]
Marcus Eriksson commented on CASSANDRA-5901:
--------------------------------------------
bq. First, I think using consistency levels as configuration options for this
might be overkill.
I kind of agree, but the reasoning was that if you usually do reads in
LOCAL_QUORUM and expect it to be consistent, it would map directly to doing
LOCAL_QUORUM bootstrap. Adding more validation that the keyspaces in the config
actually exist makes sense. No strong feelings about how to configure it,
[~kohlisankalp] - any thoughts?
bq. Second, do you think per-keyspace settings are necessary?
I don't think it would be common to manually configure each KS - it is mostly
to be able to handle different replication factors - say you have a RF=2 and a
RF=3 keyspace, it would make sense to bootstrap the RF=2 at ANY and the RF=3
one at QUORUM.
And the reason for not putting it in the schema (IIRC I did that first) would
be that if you are in a bad situation with several nodes down, you don't want
to do a schema change to be able to bootstrap a new node in
> 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]
