[
https://issues.apache.org/jira/browse/CASSANDRA-20543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-20543:
--------------------------------------
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/118535e499856fb3009887f569e51a393fccf244
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Accord: Fix issue where 3 tests would crash consistently in CI
> --------------------------------------------------------------
>
> Key: CASSANDRA-20543
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20543
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Accord
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: NA
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code}
> jvm-utests-jdk17::unit.org.apache.cassandra.db.compaction.unified.ShardedCompactionWriterTest
> jvm-utests-jdk17::unit.org.apache.cassandra.db.compaction.unified.ParallelizedTasksTest
> jvm-utests-jdk17::unit.org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest
> {code}
> These 3 tests would consistently crash in CI! In bisecting the history it
> turns out we were not properly passing “maxMemory” to the junit fork process
> so every test ran with Xmx=1g. The history changed that to respect the
> maxMemory we already had which was needed for the route index test, but this
> appears to break those test (likely caused by OOM killing).
> Lowering from 4g to 2g appears to solve the problem
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
