[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511232#comment-17511232 ]
Benjamin Lerer commented on CASSANDRA-5901: ------------------------------------------- [~marcuse] It seems that nothing has happen on this ticket since quite some time. Is your patch still valid? Do you need some help for the review? > 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: Legacy/Streaming and Messaging > Reporter: Sankalp Kohli > Assignee: Marcus Eriksson > Priority: Low > 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 (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org