[
https://issues.apache.org/jira/browse/CASSANDRA-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430058#comment-17430058
]
Ekaterina Dimitrova edited comment on CASSANDRA-17043 at 10/18/21, 3:03 PM:
----------------------------------------------------------------------------
I agree with everything said, the point for not exhausting all resources of
your organization is a good one. I don't think there is perfect answer but what
you suggest sounds reasonable. What I can suggest and add to the wiki page is
to advise to people around parallelism so they can make an informed decision
whether to use the default one or change it. What do you think?
I also looked at the current patches you posted and they look reasonable to me.
I can test also the patches later today. Thank you!
was (Author: e.dimitrova):
I agree with everything said, the point for not exhausting all resources of
your organization is a good one. I don't think there is perfect answer but what
you suggest sounds reasonable. What I can suggest and add to the wiki page is
advise to people around parallelism so they can make an informed decision
whether to use the default one or change it. What do you think?
I also looked at the current patches you posted and they look reasonable to me.
I can test also the patches later today. Thank you!
> 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
