[
https://issues.apache.org/jira/browse/CASSANDRA-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17043:
------------------------------------------
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|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.
was:
I think that the dtest multiplexer should always use the same resources than
the regular dtests. 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.
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.
> 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
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
