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

Better Behavior for GCInspector with Low Pause Time GCs

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Low
    • Resolution: Unresolved
    • 5.x
    • Local/Other
    • None
    • Operability
    • Low Hanging Fruit
    • All
    • None

    Description

      Low pause time GCs like Shenandoah tend to be very spammy when it comes to running Cassandra with the default configuration. This is because GCInspector seems to detect that Shenandoah cycles are equivalent to GC pauses and because these cycles tend to be relatively long (in the order of 2-3 seconds in my experience) GCInspector constantly throws warnings. However, these cycle times are normal and are not an indicator of resource contention or heap pressure as the actual pause times are very short.

      It would be great if Cassandra could be modified such that GCInspector had different behavior if a low pause time collector was detected as being in use (such as perhaps disabling the warning altogether).

      Note that I used Shenandoah here for my example but ZGC is presumed to have similar behavior.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned Assign to me
            reillybrogan Reilly Brogan

            Dates

              Created:
              Updated:

              Slack

                Issue deployment