[
https://issues.apache.org/jira/browse/CASSANDRA-11644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ZhaoYang updated CASSANDRA-11644:
---------------------------------
Description:
The gc_warn_threshold_in_ms is supposed to be applied 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 error logic is : Math.min(GC_WARN_THRESHOLD_IN_MS != 0 ?
GC_WARN_THRESHOLD_IN_MS : MIN_LOG_DURATION, MIN_LOG_DURATION);
The current problem is StatusLogger is logging too many info because of large
tables, changing gc_warn_threshold_in_ms doesn't help because of this issue/
was:
The gc_warn_threshold_in_ms is supposed to be applied 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 error logic is : Math.min(GC_WARN_THRESHOLD_IN_MS != 0 ?
GC_WARN_THRESHOLD_IN_MS : MIN_LOG_DURATION, MIN_LOG_DURATION);
> gc_warn_threshold_in_ms is not applied when it's greater than
> MIN_LOG_DURATION(200ms)
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11644
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11644
> Project: Cassandra
> Issue Type: Bug
> Reporter: ZhaoYang
> Assignee: ZhaoYang
> Priority: Minor
> Fix For: 2.1.15
>
> Attachments: CASSANDRA-11644.patch
>
>
> The gc_warn_threshold_in_ms is supposed to be applied 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 error logic is : Math.min(GC_WARN_THRESHOLD_IN_MS != 0 ?
> GC_WARN_THRESHOLD_IN_MS : MIN_LOG_DURATION, MIN_LOG_DURATION);
> The current problem is StatusLogger is logging too many info because of large
> tables, changing gc_warn_threshold_in_ms doesn't help because of this issue/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
