2.1.15版本,双DC的集群,读写策略是local_quorum,停掉备DC的所有节点,通过jmx监控到的写时延WriteLatency,从1毫秒上升到将近3毫秒,备DC服务启动后恢复,请问是什么原因?
2.1.15版本,双DC的集群,读写策略是local_quorum,停掉备DC的所有节点,通过jmx监控到的写时延WriteLatency,从1毫秒上升到将近3毫秒,备DC服务启动后恢复,请问是什么原因?
差异可能是因为coordinator node正在为另一个发生故障的DC存储hints。
您可以在其他clusters中一致地复制吗? 差异太低而不必担心。
The difference may be because the coordinator node is storing hints for the other DC that is down.
Is it something you can replicate consistently in other clusters? The difference is too low to worry about. Cheers!
yes. we can replicate consistently in other clusters. Thank you for your answer.
5 People are following this question.
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2023 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use