-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
As a premise, 5.0 introduced an optimization for sharded transactions to return to the client after the decision was persisted but before the participating shards commit their local storage transactions. That optimization made it incorrect for linearizable reads to ignore prepare conflicts.
I have no evidence we actually change the prepare conflict behavior for linearizable reads, but we do have code that suggests we may have at some point. That code (according to a patch run) can be deleted.
- is related to
-
SERVER-37364 Coordinator should return the decision to the client as soon as the decision is durable
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Backlog
-