[CASSANDRA-11644] gc_warn_threshold_in_ms is not applied when it's greater than MIN_LOG_DURATION(200ms)

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 2.1.15, 2.2.7, 3.0.7, 3.7
• Severity: Low
• Assignee: Zhao Yang
• Reporter: Zhao Yang

Authors

Zhao Yang

Reviewers

Joshua McKenzie

• Created: 25/Apr/16 16:03
• Updated: 16/Apr/19 09:30
• Resolved: 13/May/16 16:40

Description

The gc_warn_threshold_in_ms is supposed to be applied to StatusLogger when user specifies it. But in the source code of GCInspector, gc_warn_threshold_in_ms is used only when it is smaller than MIN_LOG_DURATION(200ms).

The current logic is : STAT_THRESHOLD = Math.min(GC_WARN_THRESHOLD_IN_MS != 0 ? GC_WARN_THRESHOLD_IN_MS : MIN_LOG_DURATION, MIN_LOG_DURATION);

My problem is that StatusLogger is logging too many info because of large tables, changing gc_warn_threshold_in_ms doesn't help because of this issue.

Issue Links

• is related to: CASSANDRA-8907 Raise GCInspector alerts to WARN