You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/08/20 17:54:56 UTC

[jira] [Resolved] (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:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-5901.
---------------------------------------

    Resolution: Duplicate

Okay, so really your problem is when bootstrap streams from a node other than the one it's replacing.  The right fix is CASSANDRA-2434.
                
> 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
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira