You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Alex Petrov (Jira)" <ji...@apache.org> on 2019/10/09 15:53:00 UTC

[jira] [Created] (CASSANDRA-15350) Add CAS “uncertainty” and “contention" messages that are currently propagated as a WriteTimeoutException.

Alex Petrov created CASSANDRA-15350:
---------------------------------------

             Summary: Add CAS “uncertainty” and “contention" messages that are currently propagated as a WriteTimeoutException.
                 Key: CASSANDRA-15350
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15350
             Project: Cassandra
          Issue Type: Improvement
          Components: Feature/Lightweight Transactions
            Reporter: Alex Petrov


Right now, CAS uncertainty introduced in https://issues.apache.org/jira/browse/CASSANDRA-6013 is propagating as WriteTimeout. One of this conditions it manifests is when there’s at least one acceptor that has accepted the value, which means that this value _may_ still get accepted during the later round, despite the proposer failure. Similar problem happens with CAS contention, which is also indistinguishable from the “regular” timeout, even though it is visible in metrics correctly.



--
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