cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Yang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-8860) Too many java.util.HashMap$Entry objects in heap
Date Fri, 27 Feb 2015 06:42:05 GMT

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

Phil Yang edited comment on CASSANDRA-8860 at 2/27/15 6:41 AM:
---------------------------------------------------------------

The heapdump is still being uploaded, I find these Entry objects is indeed generated by SizeTieredCompactionStrategy.createOverlapChain.
So do you still need the heapdump?

Besides, in the node which has this issue , there is a table which has 8935 SSTables because
this table is rarely being read.


was (Author: yangzhe1991):
The heapdump is still being uploaded, I find these Entry objects is indeed generated by SizeTieredCompactionStrategy.createOverlapChain.
So do you still need the heapdump?

Besides, in the node which has this issue , there is a table has 8935 SSTables because this
table is rarely being read.

> Too many java.util.HashMap$Entry objects in heap
> ------------------------------------------------
>
>                 Key: CASSANDRA-8860
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8860
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra 2.1.3, jdk 1.7u51
>            Reporter: Phil Yang
>            Assignee: Marcus Eriksson
>             Fix For: 2.1.4
>
>         Attachments: cassandra-env.sh, cassandra.yaml, jmap.txt, jstack.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
it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message