ReadRepairStage错误消息超时 [英] timeouts on ReadRepairStage error messages

问题描述

我们使用的是Apache Cassandra 3.11.4。最近，我们看到整个集群中的readrepair ERROR消息超载，因为我们遇到了超时问题。.我无法找到根本原因。赞赏有关此问题的任何输入..

We are using Apache Cassandra 3.11.4 .Recently we are seeing overloaded readrepair ERROR messages in the entire cluster because that we are getting timeouts ..I'm not able to find the root cause for this . Appreciate any inputs on this issue ..

错误[ReadRepairStage：2537] 2019-07-18 17：08：15,119 CassandraDaemon.java:228-线程Thread中的异常[ ReadRepairStage：2537,5，main]
org.apache.cassandra.exceptions.ReadTimeoutException：操作超时-仅收到1个响应。 org.apache.cassandra.service.DataResolver $ RepairMergeListener.close（DataResolver.java:202）中的
〜[apache-cassandra-3.11.3.jar：3.11.3] org.apache中的
。 cassandra.db.partitions.UnfilteredPartitionIterators $ 2.close（UnfilteredPartitionIterators.java:175）〜[apache-cassandra-3.11.3.jar：3.11.3]
，位于org.apache.cassandra.db.transform.BaseIterator。 close（BaseIterator.java:92）〜[apache-cassandra-3.11.3.jar：3.11.3]
at org.apache.cassandra.service.DataResolver.compareResponses（DataResolver.java:79）〜[apache -cassandra-3.11.3.jar：3.11.3]
，位于org.apache.cassandra.service.AsyncRepairCallback $ 1.runMayThrow（AsyncRepairCallback.java:50）〜[apache-cassandra-3.11.3.jar：3.11 .3] org.apache.cassandra.utils.WrappedRunnable.run（WrappedRunnable.java:28）中的
〜[apache-cassandra-3.11.3.jar：3.11.3] java.util中的
.concurrent.ThreadPoolExecutor.runWorker（ThreadPoolExecutor.java:1149）〜[na：1.8.0_212]
at java.util.concurrent.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:624）〜[na：1.8。 0 _212]
在org.apache.cassandra.concurrent.NamedThreadFactory.lambda $ threadLocalDeallocator $ 0（NamedThreadFactory.java:81）〜[apache-cassandra-3.11.3.jar：3.11.3]
在java .lang.Thread.run（Thread.java:748）〜[na：1.8.0_212]

ERROR [ReadRepairStage:2537] 2019-07-18 17:08:15,119 CassandraDaemon.java:228 - Exception in thread Thread[ReadRepairStage:2537,5,main] org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - received only 1 responses. at org.apache.cassandra.service.DataResolver$RepairMergeListener.close(DataResolver.java:202) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$2.close(UnfilteredPartitionIterators.java:175) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.db.transform.BaseIterator.close(BaseIterator.java:92) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.service.DataResolver.compareResponses(DataResolver.java:79) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.service.AsyncRepairCallback$1.runMayThrow(AsyncRepairCallback.java:50) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) ~[apache-cassandra-3.11.3.jar:3.11.3] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_212] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_212] at org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) ~[apache-cassandra-3.11.3.jar:3.11.3] at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_212]

将dclocalreadrepair减少为0.0

reduced dclocalreadrepair to 0.0

推荐答案

超时是尝试修复时的常见问题，如果没有错误的更多详细信息或您的配置，这将是一团糟。

Timeouts are a common issue while attempting repairs, and without more specifics of the errors, or your configuration, this will be a shot in the dark.

• 修复取决于磁盘空间，因为它将创建文件的临时副本，根据经验，磁盘利用率应低于或等于50％以确保您有足够的空间。


• 如果群集受到压力，则修复可能会延迟/中止，在这种情况下，您可能需要扩大群集以增加可用资源。


• 您可能想看看 Aaron 有关修复中JVM设置的更新。

• Repairs depend on disk space, as it will create temporary copies of files, as a rule of thumb the disk utilization should be lower than or equal to 50% to ensure that you'll have enough space.
• Repairs can be delayed/aborted if the cluster is stressed, if that is the case, you may need to scale up the cluster to increase the available resources.
• You may want to take a look in these other recommendations from Aaron regarding updates of the JVM settings in repairs.

自Cassandra 3.11.3起，设置 read_repair_chance 和 dc_read_repair_chance 的设置为已删除，因为它们的名称会误导所获得的结果。添加它们不会有任何效果。

Also note that since Cassandra 3.11.3, the settings read_repair_chance and dc_read_repair_chance were removed, as their names were misleading with the result obtained. Adding them won't have any effect.

这篇关于ReadRepairStage错误消息超时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！