cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sankalp kohli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node
Date Fri, 24 Apr 2015 01:24:38 GMT

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

sankalp kohli commented on CASSANDRA-5901:
------------------------------------------

That would be ideal however if repair is not run for a long time, it will cause lot of data
to be streamed. Also an option to stream from local DC only or number of nodes will be good
to have. 

> 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
>          Components: Core
>            Reporter: sankalp kohli
>            Assignee: Yuki Morishita
>            Priority: Minor
>
> 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.3.4#6332)

Mime
View raw message