You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "sharanya (Jira)" <ji...@apache.org> on 2021/02/08 16:23:00 UTC

[jira] [Commented] (CASSANDRA-16430) Cassandra JVM Memory Pools -Par Survivor Space UsedPoolMemory

    [ https://issues.apache.org/jira/browse/CASSANDRA-16430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281174#comment-17281174 ] 

sharanya commented on CASSANDRA-16430:
--------------------------------------

Hi [~brandon.williams],

Thanks for the valued information.

 

 

> Cassandra JVM Memory Pools -Par Survivor Space UsedPoolMemory
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-16430
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16430
>             Project: Cassandra
>          Issue Type: Task
>          Components: Local/Config, Observability/Metrics
>            Reporter: sharanya
>            Priority: Urgent
>
> I have a 9 node cluster of cassandra, with 2gb of data on each node in our production environment. We are continuously facing below warnings from one of our monitoring tool, but there is no suspicious error from system.log file. Also there is sufficient memory available for Heap/server.
>  
>  warn - Cassandra JVM Memory Pools -Par Survivor Space UsedPoolMemory
> Datasource: Cassandra JVM Memory Pools -Par Survivor Space
> Datapoint: UsedPoolMemory
> Level: warn
> Start: 2021-02-08 10:11:17 GMT
> Duration: 1h 0m
> Value: 100.0
> ClearValue: 1.3631
> Reason: UsedPoolMemory is not >= 90: the current value is 1.3631
> The java memory pool Par Survivor Space on esg3-c-cassv3-03p is now using 100.0 % of the maximum.
>  
> We see the below message in debug.log file.
> 2021-02-08 08:43:51,310 INFO  [ReadStage-1] NoSpamLogger.java:91 - Maximum memory usage reached (512.000MiB), cannot allocate chunk of 1.000MiB
> 2021-02-08 08:47:28,344 DEBUG [COMMIT-LOG-ALLOCATOR] AbstractCommitLogSegmentManager.java:109 - No segments in reserve; creating a fresh one
>  
>  
> Please help us to fix this issue ASAP.
>  
>  
>  
> Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org