Benedict Elliott Smith created CASSANDRA-19296: --------------------------------------------------
Summary: Accord: Improve and Document CoordinateShardDurable semantics Key: CASSANDRA-19296 URL: https://issues.apache.org/jira/browse/CASSANDRA-19296 Project: Cassandra Issue Type: Improvement Components: Accord Reporter: Benedict Elliott Smith Firstly, CoordinateShardDurable should retry in future epochs if necessary. In principle this isn't a problem; the next CoordinateShardDurable should pick up where this one left-off. But we should consider the logic very carefully, and anyway not leave dangling waits. We should also carefully consider the special-case where replicas are bootstrapping in the future and we are coordinating the shard durability. This replica should safely participate in the sync point, waiting for only the transactions it requires to be replicated to it. So this should also function as expected, but this should be tested and documented carefully. -- 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