[
https://issues.apache.org/jira/browse/CASSANDRA-20980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038705#comment-18038705
]
Dmitry Konstantinov commented on CASSANDRA-20980:
-------------------------------------------------
CI run results:
[https://pre-ci.cassandra.apache.org/job/cassandra/167/#showFailuresLink]
[^CASSANDRA-20980_ci_summary.htm]
[^CASSANDRA-20980_results_details.tar.xz]
The test failures are not related to the changes:
Tests / jvm-dtest jdk17 1/16 /
org.apache.cassandra.distributed.test.accord.MigrationFromAccordWriteRaceTest.testSplitAndRetryNonSerialLoggedBatchTwoTablesTwoPkey-_jdk17_x86_64
Tests / jvm-dtest jdk17 1/16 /
org.apache.cassandra.fuzz.sai.AccordFullSingleNodeSAITest.indexOnlySaiTest-cassandra.testtag_IS_UNDEFINED
Tests / jvm-dtest jdk17 4/16 /
org.apache.cassandra.distributed.test.CASMultiDCTest.testLocalSerialLocalCommit-_jdk17_x86_64
Tests / simulator-dtest jdk11 /
org.apache.cassandra.simulator.test.HarrySimulatorTest.test-_jdk11_x86_64
Tests / jvm-dtest jdk17 8/16 /
org.apache.cassandra.fuzz.topology.AccordBootstrapTest.bootstrapFuzzTest-_jdk17_x86_64
Tests / simulator-dtest jdk11 /
org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest-cassandra.testtag_IS_UNDEFINED
Tests / simulator-dtest jdk11 /
org.apache.cassandra.simulator.test.ShortAccordSimulationTest.simulationTest-_jdk11_x86_64
Tests / dtest jdk11 34/64 /
dtest.client_request_metrics_test.TestClientRequestMetrics.test_client_request_metrics
Tests / dtest jdk17 34/64 /
dtest.client_request_metrics_test.TestClientRequestMetrics.test_client_request_metrics
> GCInspector should use different thresholds on GC events for warning messages
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-20980
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20980
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Observability/Logging
> Reporter: Yuqi Yan
> Assignee: Yuqi Yan
> Priority: Normal
> Fix For: 5.x
>
> Attachments: CASSANDRA-20980_ci_summary.htm,
> CASSANDRA-20980_results_details.tar.xz, debug_logging_gc_inspector.patch,
> gc_g1.log, gc_shenandoah.log, gc_zgc.log, system_g1.log,
> system_shenandoah.log, system_zgc.log
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Running Cassandra 4.1 and recently testing with ShenandoahGC.
> Noticed that the log message is flooded with the warning message coming from
> GCInspector.
> Taking a closer look, that seems that we're warning on every GC event that
> takes longer than 1 second (default). And from document that the intention
> was to monitor GC pause time.
> But for ShenandoahGC and ZGC, there are concurrent phases (no STW) and phases
> that actually STW.
> For those concurrent phases, it's expected to take longer time (if we're on
> the non-generational version), and I feel that these phases:
> 1. require STW
> 2. doesn't require STW
> should use different thresholds in warning message.
> At least to me, phases require STW actually pause the thread, and should use
> lower threshold compared to those concurrent phases.
> Will share a patch soon
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
