You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2021/09/29 17:33:00 UTC
[jira] [Updated] (CASSANDRA-11016) Fix flapping dtests with
"unavailable" and "cannot achieve consistency" errors
[ https://issues.apache.org/jira/browse/CASSANDRA-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-11016:
-----------------------------------------
Resolution: Cannot Reproduce
Status: Resolved (was: Open)
This no longer occurs.
> Fix flapping dtests with "unavailable" and "cannot achieve consistency" errors
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-11016
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11016
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Jim Witschey
> Priority: Normal
>
> A number of dtests flap when they run a query and get an unavailable exception or can't meet a particular CL. Examples include:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/470/testReport/replace_address_test/TestReplaceAddress/replace_first_boot_test/
> http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/488/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3/range_tombstones_test/
> This seems to be a different issue than CASSANDRA-10730 -- bumping instance sizes to m3.2xl stopped that class of error, but bumping instance sizes to i2.4xl did not stop the errors described here.
> I'm probably the best person to tackle this, but won't get to it for a bit, so [~philipthompson] might take it if he has time sooner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org