cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11644) gc_warn_threshold_in_ms is not applied when it's greater than MIN_LOG_DURATION(200ms)
Date Fri, 13 May 2016 16:41:12 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joshua McKenzie updated CASSANDRA-11644:
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.7
                   3.7
                   2.2.7
           Status: Resolved  (was: Patch Available)

LGTM - committed. Thanks!

> 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, 2.2.7, 3.7, 3.0.7
>
>         Attachments: CASSANDRA-11644.patch
>
>
> 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.



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

Mime
View raw message