JVM_OPTS="$JVM_OPTS -Dcassandra.consistent.rangemovement=false 有什么用
what is the use of JVM_OPTS="$JVM_OPTS -Dcassandra.consistent.rangemovement=false
谁能解释一下
有什么用
-JVM_OPTS="$JVM_OPTS -Dcassandra.consistent.rangemovement=false"
默认设置是什么?它如何影响多个节点加入集群?
我得到的所有相关信息是Datastax doc for cassandra utility
根据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
).
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_OPTS="$JVM_OPTS -Dcassandra.consistent.rangemovement=false"
默认设置是什么?它如何影响多个节点加入集群?
我得到的所有相关信息是Datastax doc for cassandra utility
根据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
).
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
.