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

问题描述

我在cassandra的debug.log中连续看到此错误，

  WARN [SharedPool-Worker-2] 2018- 05-16 08：33：48,585 BatchStatement.java:287-为[test，test1]准备的语句的大小为6419，比指定的阈值5120超出了1299。
  

在此

 其中，
 6419-输入有效负载大小（批量）
 5120-阈值大小
 1299-字节大小超出阈值
  

按照卡桑德拉（Cassandra）中的这张票， https：// github。 com / krasserm / akka-persistence-cassandra / issues / 33 我看到这是由于输入有效负载大小增加所致，所以我增加了cassandra中的 commitlog_segment_size_in_mb .yml到 60mb ，我们不再面临此警告。

此警告有害吗？

解决方案

这与提交日志大小没有直接关系，我想知道为什么吗？

解决方案

它的更改导致警告消失。

批处理大小阈值由 batch_size_warn_threshold_in_kb 参数控制默认值为5kb（5120字节）。

您可以将该参数增加为更高的值，但是您确实有充分的理由使用批处理-理解起来很高兴用法的上下文...

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.

In this

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

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.

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...

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屋！