[CASSANDRA-17043] CircleCI dtest multiplexer with MIDRES needs more resources

• Type: Task
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.0.26, 3.11.12, 4.0.2, 4.1-alpha1, 4.1
• Component/s: CI
• Change Category: Quality Assurance
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/ee6cd06afb66317212d681117d460afebf1ceb31

Test and Documentation Plan

The ticket includes multiplexer runs for a dtest that needs MIDRES

• Assignee: Andres de la Peña
• Reporter: Andres de la Peña

Authors

Andres de la Peña

Reviewers

Ekaterina Dimitrova

• Created: 14/Oct/21 16:07
• Updated: 27/May/22 19:25
• Resolved: 19/Oct/21 10:54

Description

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 when trying to repeatedly run a resource-hungry dtest, or like this other one 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.

 

Issue Links

• Discovered while testing: CASSANDRA-16334 Replica failure causes timeout on multi-DC write