[
https://issues.apache.org/jira/browse/CASSANDRA-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349220#comment-14349220
]
Robert Coli commented on CASSANDRA-8860:
----------------------------------------
{quote}We should probably remove this feature alltogether (cold_reads_to_omit),
using DTCS suits these kinds of workloads much better{quote}
For the record (not that anyone asked... ;D) I am +1 here; seems like lots of
complexity for a questionable potential win, and initial implementation has
exposed some serious potential edge cases. DTCS FTW.
> 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)
