[
https://issues.apache.org/jira/browse/CASSANDRA-15977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215481#comment-17215481
]
Andres de la Peña commented on CASSANDRA-15977:
-----------------------------------------------
I can't think of a lot of things to optimize the runtime of the tests. They
take long because of the parameterization for strategies, coordinator
selection, ordering, etc. There are 16 parameter combinations for each of the
34 tested query types, which gives those 544 tests. All the tests share the
same cluster instance, which makes them run quite fast. That's still around
10min total with around 1sec per test, which is over the current 6min timeout.
We could try to parallelize the execution, but that's not going to reduce the
workload. Probably the easiest way to reduce the number of tests in reducing
the number of tested parameters with NONE repair strategy, since those cases
are less interesting.
> 4.0 quality testing: Read Repair
> --------------------------------
>
> Key: CASSANDRA-15977
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15977
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/java, Test/unit
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 13h 20m
> Remaining Estimate: 0h
>
> This is a subtask of CASSANDRA-15579 focusing on read repair.
> [This
> document|https://docs.google.com/document/d/1-gldHcdLSMRbDhhI8ahs_tPeAZsjurjXr38xABVjWHE/edit?usp=sharing]
> lists and describes the existing functional tests for read repair, so we can
> have a broad view of what is currently covered. We can comment on this
> document and add ideas for new cases/tests, so it can gradually evolve to a
> more or less detailed test plan.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
