cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "graham sanderson (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-8860) Too many java.util.HashMap$Entry objects in heap
Date Thu, 05 Mar 2015 02:53:38 GMT

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

graham sanderson edited comment on CASSANDRA-8860 at 3/5/15 2:53 AM:
---------------------------------------------------------------------

Note we are going to try a simpler patch on 2.1.3 (because we believe we are seeing this too,
though our heaps are simply too big to dump reasonably it would seem). We're just reverting
the cold_reads_to_omit default to 0.0, and adding logging.

We could probably change the schema for all tables to do this explicitly, but I haven't looked
at whether this affects LCS L0

This is just an FYI to see if it helps us - we are seeing memory issue that we did not see
in testing with 2.1.3, but may well be related to a proliferation of sstables


was (Author: graham sanderson):
Note we are going to try a simpler patch on 2.1.3 (because we believe we are seeing this too,
though our heaps are simply too big to dump reasonably it would seem). We're just reverting
the cold_reads_to_omit default to 0.0, and adding logging.

We could probably change the schema for all tables to do this explicitly, but I haven't looked
at whether this affects LCS L0

> 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: 0001-remove-cold_reads_to_omit.patch, 8860-v2.txt, 8860.txt, cassandra-env.sh,
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
it.



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

Mime
View raw message