[
https://issues.apache.org/jira/browse/CASSANDRA-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382550#comment-15382550
]
Wei Deng commented on CASSANDRA-12221:
--------------------------------------
It doesn't *directly* indicate a problem, so it shouldn't be WARN/ERROR level
logging. (Indirectly there could still be a problem on your cluster and this
could be one of the symptoms.) See some more discussions in CASSANDRA-11681 and
CASSANDRA-11940. TL;DR is the default 512MB setting is not always optimal.
Also, unless your analysis has revealed a real bug with the code, this kind of
question is best asked on user mailing list, instead of tracking it in JIRA.
> Maximum Memory Usage Reached - NoSpamLogger
> -------------------------------------------
>
> Key: CASSANDRA-12221
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12221
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: CentOS 6.8 x86_64, Cassandra-3.0.7
> Reporter: vin01
> Priority: Minor
>
> I see some logs which look like :-
> INFO [SharedPool-Worker-22] 2016-07-17 22:03:02,725 NoSpamLogger.java:91 -
> Maximum memory usage reached (536870912 bytes), cannot allocate chunk of
> 1048576 bytes
> INFO [SharedPool-Worker-33] 2016-07-17 22:18:02,747 NoSpamLogger.java:91 -
> Maximum memory usage reached (536870912 bytes), cannot allocate chunk of
> 1048576 bytes
> INFO [SharedPool-Worker-35] 2016-07-17 22:33:02,829 NoSpamLogger.java:91 -
> Maximum memory usage reached (536870912 bytes), cannot allocate chunk of
> 1048576 bytes
> INFO [SharedPool-Worker-31] 2016-07-17 22:48:02,834 NoSpamLogger.java:91 -
> Maximum memory usage reached (536870912 bytes), cannot allocate chunk of
> 1048576 bytes
> When i get these logs, CPU usage is quite high on the system.
> Are they expected? Log message also seems confusing and i am not sure what
> memory we are talking about here..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
