Benedict Elliott Smith created CASSANDRA-20726:
--------------------------------------------------

             Summary: Accord: Fast Coordination Optimisations and Miscellaneous 
Fixes
                 Key: CASSANDRA-20726
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20726
             Project: Apache Cassandra
          Issue Type: Improvement
          Components: Accord
            Reporter: Benedict Elliott Smith


    Improve:
     - Introduce SequentialAgentExecutor
     - ExecuteEphemeralRead.LocalExecute (matching ExecuteTxn.LocalExecute)
     - remove AgentExecutor (agent() only used as implementation detail)
     - Skip CommandStore/CommandsForKey on read or apply, when safe to do so
     - Implement maybeExecuteImmediately
    Fix:
     - Marking vestigial without knowing all covering keys
     - Incorrect size in WaitingOn.none
     - Cleanup RX that are not known but are no longer needed, due to being 
defunct
     - Home should not abort because of local truncation; may still be 
incomplete on another shard
     - Invalidate infinite loop due to interpreting Vestigial as a possible 
decision (as though it were another Truncated state)
     - Known.isTruncated reporting incorrect answer in some cases, leading to 
infinite RecoverWithRoute loops as not slicing to correct subset and some 
shards are truncated and reject the deps collection
     - BurnTest slowCoordinatorDelay should grow with retryCount
     - NotAccept should check both ballot and saveStatus; PreCommitted or later 
can be propagated by Apply that has an earlier ballot
     - Handle awaiting locally retired epoch
     - Fix propagate low epoch of sync points
     - Fix GetEphemeralReadDeps.reduce NPE
     - Don't use tombstones to ERASE journal entries, as want to produce an 
Erased SaveStatus until EXPUNGE




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to