[
https://issues.apache.org/jira/browse/CASSANDRA-19718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-19718:
--------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: API /
Semantic Implementation(12988)
Complexity: Low Hanging Fruit
Discovered By: Fuzz Test
Fix Version/s: NA
Severity: Low
Status: Open (was: Triage Needed)
> SyncPoint timeouts become a Exhausted rather than a Timeout and doesn’t get
> retried
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-19718
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19718
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: NA
>
>
> In Cassandra we try to make sure coordinators return timeout if every call
> under it was also a timeout, this makes it easier to understand what is going
> on (coordination failure due to timeouts looks very different than us just
> timing out), but accord doesn't do this; leading to an Exhausted error (which
> we don't retry)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
