You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Blake Eggleston (Jira)" <ji...@apache.org> on 2025/02/28 22:11:00 UTC
[jira] [Created] (CASSANDRA-20376) CEP-45: Logged read speculation
Blake Eggleston created CASSANDRA-20376:
-------------------------------------------
Summary: CEP-45: Logged read speculation
Key: CASSANDRA-20376
URL: https://issues.apache.org/jira/browse/CASSANDRA-20376
Project: Apache Cassandra
Issue Type: New Feature
Components: Consistency/Coordination
Reporter: Blake Eggleston
In additional to the normal read speculation, read coordinators should also immediately speculate if they receive a response from a replica that's so far behind that it wouldn't be practical to catch them up via read reconciliation. Which read responses should be speculatively retried on other replicas should become clearer with each response / mutation summary we receive from read participants.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org