Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-11644

gc_warn_threshold_in_ms is not applied when it's greater than MIN_LOG_DURATION(200ms)

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Low
    • Resolution: Fixed
    • Fix Version/s: 2.1.15, 2.2.7, 3.0.7, 3.7
    • Component/s: None
    • Labels:
      None
    • Severity:
      Low

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jasonstack ZhaoYang
                Reporter:
                jasonstack ZhaoYang
                Authors:
                ZhaoYang
                Reviewers:
                Joshua McKenzie
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: