Cassandra:NoSpamLogger日志达到最大内存使用量 [英] Cassandra: NoSpamLogger log Maximum memory usage reached
问题描述
每隔15分钟我会看到此日志条目:
Every 15 min I see this log entry:
2018-07-30 10:29:57,529信息[pool-1-thread-2] NoSpamLogger.java:91日志已达到最大内存使用率(512.000MiB)，无法分配1.000MiB的块
2018-07-30 10:29:57,529 INFO [pool-1-thread-2] NoSpamLogger.java:91 log Maximum memory usage reached (512.000MiB), cannot allocate chunk of 1.000MiB
我一直在阅读此问题，但是我的表看不到任何错误: NoSpamLogger.java达到Cassandra的最大内存使用量
I´ve been reading through this Question, but I cant see anything wrong with my tables: NoSpamLogger.java Maximum memory usage reached Cassandra
我有4个大桌子:
iot_data/derived_device_data histograms
Percentile SSTables Write Latency Read Latency Partition Size Cell Count
(micros) (micros) (bytes)
50% 0.00 0.00 0.00 642 12
75% 0.00 0.00 0.00 17084 642
95% 0.00 0.00 0.00 263210 11864
98% 0.00 0.00 0.00 1629722 61214
99% 0.00 0.00 0.00 1955666 88148
Min 0.00 0.00 0.00 150 0
Max 0.00 0.00 0.00 4055269 152321
iot_data/derived_device_data_by_year histograms
Percentile SSTables Write Latency Read Latency Partition Size Cell Count
(micros) (micros) (bytes)
50% 0.00 0.00 0.00 51012 1597
75% 0.00 0.00 0.00 2346799 61214
95% 0.00 0.00 0.00 52066354 1629722
98% 0.00 0.00 0.00 52066354 1629722
99% 0.00 0.00 0.00 52066354 1629722
Min 0.00 0.00 0.00 6867 216
Max 0.00 0.00 0.00 52066354 1629722
iot_data/device_data histograms
Percentile SSTables Write Latency Read Latency Partition Size Cell Count
(micros) (micros) (bytes)
50% 0.00 29.52 0.00 2299 149
75% 0.00 42.51 0.00 182785 9887
95% 0.00 61.21 0.00 2816159 152321
98% 0.00 61.21 0.00 4055269 219342
99% 0.00 61.21 0.00 17436917 1131752
Min 0.00 17.09 0.00 43 0
Max 0.00 61.21 0.00 74975550 4866323
iot_data/device_data_by_week_sensor histograms
Percentile SSTables Write Latency Read Latency Partition Size Cell Count
(micros) (micros) (bytes)
50% 0.00 35.43 0.00 8239 446
75% 0.00 51.01 0.00 152321 8239
95% 0.00 61.21 0.00 2816159 152321
98% 0.00 61.21 0.00 4055269 219342
99% 0.00 61.21 0.00 12108970 785939
Min 0.00 20.50 0.00 43 0
Max 0.00 61.21 0.00 74975550 4866323
尽管我知道，派生的设备数据表//派生的设备数据表_by_year表需要一些重构，但它们都没有接近100MB的标记.为什么我会收到此日志条目?
Altough I know that the derived_device_data // derived_device_data_by_year tables need some refactoring, none of them is close to the 100MB mark. Why am I getting this log entry though?
我在测试系统上注意到了相同的日志条目，它们几乎没有数据运行，但配置与prod相同.12GB RAM，cassandra 3.11.2
I noticed the same log entry on my test systems, which are running almost without data but with the same configuration as prod. 12GB RAM, cassandra 3.11.2
推荐答案
您可能需要检查 vm.max_map_count 的值以及交换设置.如果启用了交换，则可能会影响两个系统的性能. vm.max_map_count 的默认值也可能太低，并且会影响Cassandra和Elasticsearch(请参阅
You may need to check the value of vm.max_map_count and and settings for swap. If swap is enabled, then it could affect performance of the both systems. Default value of vm.max_map_count could be also too low, and affect both Cassandra and Elasticsearch (see recommendation for ES).
此外，您可能需要显式设置Cassandra和 file_cache_size_in_mb 的堆大小-具有12Gb RAM，Cassandra将使用1/4即3Gb，而 file_cache_size_in_mb 将是〜750Mb(堆的1/4)-可能太低了.
Also, you may need explicitly set heap size for Cassandra and file_cache_size_in_mb - with 12Gb RAM, Cassandra will use 1/4 that is 3Gb, and file_cache_size_in_mb will be ~750Mb (1/4 of heap) - that could be too low.
P.S.因为它被记录为 INFO ，所以它被认为是无害的.参见 https://issues.apache.org/jira/browse/CASSANDRA-12221& https://issues.apache.org/jira/browse/CASSANDRA-11681
P.S. Because it's logged as INFO, then it's considered harmless. See https://issues.apache.org/jira/browse/CASSANDRA-12221 & https://issues.apache.org/jira/browse/CASSANDRA-11681
这篇关于Cassandra:NoSpamLogger日志达到最大内存使用量的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
