Can anyone explain what is the use of
谁能解释一下有什么用呢？
-JVM_OPTS="$JVM_OPTS -Dcassandra.consistent.rangemovement=false"
What is the default setting and how does it effect multiple nodes joining a cluster?
什么是默认设置以及它如何影响加入群集的多个节点？
All i got related to this is Datastax doc for cassandra utility
所有与此相关的是用于cassandra实用程序的Datastax doc
1 个解决方案
#1
4
According to NEWS.txt
根据NEWS.txt
Bootstrapping now ensures that range movements are consistent, meaning the data for the new node is taken from the node that is no longer a responsible for that range of keys. If you want the old behavior (due to a lost node perhaps) you can set the following property (
-Dcassandra.consistent.rangemovement=false).Bootstrapping现在可确保范围移动一致，这意味着新节点的数据取自不再负责该范围键的节点。如果您想要旧的行为（可能是由于节点丢失），您可以设置以下属性（-Dcassandra.consistent.rangemovement = false）。
And following official operating guide
并遵循官方操作指南
After the tokens are allocated, the joining node will pick current replicas of the token ranges it will become responsible for to stream data from. By default it will stream from the primary replica of each token range in order to guarantee data in the new node will be consistent with the current state.
在分配令牌之后，加入节点将选择将负责从中流式传输数据的令牌范围的当前副本。默认情况下，它将从每个令牌范围的主副本流中传输，以保证新节点中的数据与当前状态保持一致。
In the case of any unavailable replica, the consistent bootstrap process will fail. To override this behavior and potentially miss data from an unavailable replica, set the JVM flag
-Dcassandra.consistent.rangemovement=false.如果任何不可用的副本，则一致的引导过程将失败。要覆盖此行为并可能遗漏来自不可用副本的数据，请设置JVM标志-Dcassandra.consistent.rangemovement = false。
#1
4
According to NEWS.txt
根据NEWS.txt
Bootstrapping now ensures that range movements are consistent, meaning the data for the new node is taken from the node that is no longer a responsible for that range of keys. If you want the old behavior (due to a lost node perhaps) you can set the following property (
-Dcassandra.consistent.rangemovement=false).Bootstrapping现在可确保范围移动一致，这意味着新节点的数据取自不再负责该范围键的节点。如果您想要旧的行为（可能是由于节点丢失），您可以设置以下属性（-Dcassandra.consistent.rangemovement = false）。
And following official operating guide
并遵循官方操作指南
After the tokens are allocated, the joining node will pick current replicas of the token ranges it will become responsible for to stream data from. By default it will stream from the primary replica of each token range in order to guarantee data in the new node will be consistent with the current state.
在分配令牌之后，加入节点将选择将负责从中流式传输数据的令牌范围的当前副本。默认情况下，它将从每个令牌范围的主副本流中传输，以保证新节点中的数据与当前状态保持一致。
In the case of any unavailable replica, the consistent bootstrap process will fail. To override this behavior and potentially miss data from an unavailable replica, set the JVM flag
-Dcassandra.consistent.rangemovement=false.如果任何不可用的副本，则一致的引导过程将失败。要覆盖此行为并可能遗漏来自不可用副本的数据，请设置JVM标志-Dcassandra.consistent.rangemovement = false。