[
https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510017#comment-14510017
]
sankalp kohli commented on CASSANDRA-5901:
------------------------------------------
One of the fixes for this could be that once we have better consistency in
repaired data in 3.0, we can stream the repaired data from one machine and non
repaired data from configurable number of machines.
It will also be good to have a command for the operator to find out how much
extra data will be streamed for various number of machines.
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
