Cassandra 批处理准备语句大小警告 [英] Cassandra batch prepared statement size warning

问题描述

我在 cassandra 的 debug.log 中不断看到这个错误，

I see this error continuously in the debug.log in cassandra,

WARN  [SharedPool-Worker-2] 2018-05-16 08:33:48,585 BatchStatement.java:287 - Batch of prepared statements for [test, test1] is of size 6419, exceeding specified threshold of 5120 by 1299.

在这个

   where,
                    6419 - Input payload size (Batch)
                    5120 - Threshold size
                    1299 - Byte size above threshold value

因此根据 Cassandra 中的这张票，https://github.com/krasserm/akka-persistence-cassandra/issues/33 我看到这是由于输入有效载荷大小的增加，所以我将 cassandra.yml 中的 commitlog_segment_size_in_mb 增加到 60mb 并且我们不再面临此警告.

so as per this ticket in Cassandra, https://github.com/krasserm/akka-persistence-cassandra/issues/33 I see that it is due to the increase in input payload size so I Increased the commitlog_segment_size_in_mb in cassandra.yml to 60mb and we are not facing this warning anymore.

此警告有害吗?增加 commitlog_segment_size_in_mb 会影响性能吗?

Is this Warning harmful? Increasing the commitlog_segment_size_in_mb will it affect anything in performance?

推荐答案

这个和提交日志的大小没有直接关系，我想知道为什么它的变化会导致警告消失...

This is not related to the commit log size directly, and I wonder why its change lead to disappearing of the warning...

批量大小阈值由 batch_size_warn_threshold_in_kb 参数控制，默认为 5kb(5120 字节).

The batch size threshold is controlled by batch_size_warn_threshold_in_kb parameter that is default to 5kb (5120 bytes).

您可以将此参数增加到更高的值，但您确实需要有充分的理由使用批处理 - 了解它们的使用上下文会很好...

You can increase this parameter to higher value, but you really need to have good reason for using batches - it would be nice to understand the context of their usage...

这篇关于Cassandra 批处理准备语句大小警告的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！