[CASSANDRA-8860] Remove cold_reads_to_omit from STCS

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.5
• Component/s: Local/Compaction

Environment

Cassandra 2.1.3, jdk 1.7u51

• Severity: Normal
• Assignee: Marcus Eriksson
• Reporter: Phil Yang

Authors

Marcus Eriksson

Reviewers

Tom Hobbs

• Created: 24/Feb/15 19:47
• Updated: 16/Apr/19 09:31
• Resolved: 04/Mar/15 08:10

Description

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.

Issue Links

• is duplicated by: CASSANDRA-9033 Upgrading from 2.1.1 to 2.1.3 with LCS and many sstable files makes nodes unresponsive
• is related to: CASSANDRA-8635 STCS cold sstable omission does not handle overwrites without reads
• relates to: CASSANDRA-9203 Removing cold_reads_to_omit is not backwards compatible