Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-15350

Separate exceptions for CAS write timeout exceptions caused by contention and unkown result

    XMLWordPrintableJSON

Details

    Description

      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.

      Attachments

        1. Utf8StringEncodeBench.java
          4 kB
          Yifan Cai

        Issue Links

          Activity

            People

              yifanc Yifan Cai
              ifesdjeen Alex Petrov
              Yifan Cai
              Alex Petrov, Dinesh Joshi
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 0.5h
                  0.5h