Alex Petrov created CASSANDRA-15350:

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

Right now, CAS uncertainty introduced in 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

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to