[
https://issues.apache.org/jira/browse/CASSANDRA-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483827#comment-17483827
]
Branimir Lambov commented on CASSANDRA-17164:
---------------------------------------------
This is okay. I'm writing documentation with proofs, and having them separated
makes things a little harder to prove. However, it's not hard to map what we
actually do to the proof's definitions, so I added an explanation instead.
I've reached this far:
[https://github.com/blambov/cassandra/blob/17164-trunk/src/java/org/apache/cassandra/service/paxos/Paxos.md]
I need some clarification on read commutativity/concurrent reads. It looks like
we use "promised" (i.e. the read promise) when we decide acceptance of a
proposal (the JavaDoc description also says so). This is sensible and correct
and appears necessary, but does this not mean that no reads can actually
execute concurrently? In other words, do we really gain anything by storing
read promises separately?
If we do skip proposing on a "safe" read, this is not a problem, but this
optimization does not appear to require the commutativity.
> CEP-14: Paxos Improvements
> --------------------------
>
> Key: CASSANDRA-17164
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17164
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, Consistency/Repair
> Reporter: Benedict Elliott Smith
> Assignee: Benedict Elliott Smith
> Priority: Normal
> Fix For: 4.1
>
>
> This ticket encompasses work for [CEP-14|
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
