[ https://issues.apache.org/jira/browse/CASSANDRA-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430471#comment-17430471 ]
Andres de la Peña commented on CASSANDRA-17043: ----------------------------------------------- Thanks for the review :) Committed to 3.0 as [ee6cd06afb66317212d681117d460afebf1ceb31|https://github.com/apache/cassandra/commit/ee6cd06afb66317212d681117d460afebf1ceb31] and merged to [3.11|https://github.com/apache/cassandra/commit/7e95c92d00df83d8333852e37813a871a1aada93], [4.0|https://github.com/apache/cassandra/commit/72f3b7901879aba902f92b45215a25ee130ff057] and [trunk|https://github.com/apache/cassandra/commit/3a950b45c321e051a9744721408760c568c05617]. There was a little typo on 3.0/MIDRES wrongly changing the parallelism for {{repeated_upgrade_dtest}} on 3.0/MIDRES to 100, while we want to keep the original 25. I have fixed it on commit. > CircleCI dtest multiplexer with MIDRES needs more resources > ----------------------------------------------------------- > > Key: CASSANDRA-17043 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17043 > Project: Cassandra > Issue Type: Task > Components: CI > Reporter: Andres de la Peña > Assignee: Andres de la Peña > Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > The CircleCI jobs for regular dtests jobs have more resources in MIDRES, > which is necessary for some dtests to reliably success. However, the dtest > multiplexer uses the same resources for LOWRES and MIDRES. > I think that the dtest multiplexer should always use the same resources as > the regular dtests. Using too small resources in the multiplexer can lead to > failures that don't reproduce in the regular dtest jobs, like the one we > found in > [CASSANDRA-16334|https://app.circleci.com/pipelines/github/adelapena/cassandra/1020/workflows/63908694-e4d7-40b1-9418-7a4b87826233/jobs/9422] > when trying to repeatedly run a resource-hungry dtest, or like [this other > one|https://app.circleci.com/pipelines/github/adelapena/cassandra/1020/workflows/63908694-e4d7-40b1-9418-7a4b87826233/jobs/9422] > while running {{test_network_topology}}. > This happens because I forgot to update the diff patch when adding the > multiplexer. This doesn't affect HIGHRES because in that case the patch > changes the configuration of the test executor, while in MIDRES a new > executor is defined. > -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org