[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625764#comment-14625764 ]
Jonathan Ellis commented on CASSANDRA-5901: ------------------------------------------- Isn't your proposed alternative leveraging incremental repair state to not suck? Incremental repair makes normal repair not suck too. :) > 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)