cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yaron Gueta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8860) Too many java.util.HashMap$Entry objects in heap
Date Sat, 02 May 2015 10:14:06 GMT


Yaron Gueta commented on CASSANDRA-8860:

In our testing environment we noticed that it causes a huge pressure on the GC with x4 cpu
consumption than a version without the cold_reads_to_omit feature. Once we set it to 0, the
problem solved. Thanks.

> Too many java.util.HashMap$Entry objects in heap
> ------------------------------------------------
>                 Key: CASSANDRA-8860
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra 2.1.3, jdk 1.7u51
>            Reporter: Phil Yang
>            Assignee: Marcus Eriksson
>             Fix For: 2.1.5
>         Attachments: 0001-remove-cold_reads_to_omit.patch, 8860-v2.txt, 8860.txt,,
cassandra.yaml, jmap.txt, jstack.txt, jstat-afterv1.txt, jstat-afterv2.txt, jstat-before.txt
> While I upgrading my cluster to 2.1.3, I find some nodes (not all) may have GC issue
after the node restarting successfully. Old gen grows very fast and most of the space can
not be recycled after setting its status to normal immediately. The qps of both reading and
writing are very low and there is no heavy compaction.
> Jmap result seems strange that there are too many java.util.HashMap$Entry objects in
heap, where in my experience the "[B" is usually the No1.
> If I downgrade it to 2.1.1, this issue will not appear.
> I uploaded conf files and jstack/jmap outputs. I'll upload heap dump if someone need

This message was sent by Atlassian JIRA

View raw message