[ 
https://issues.apache.org/jira/browse/CASSANDRA-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482504#comment-17482504
 ] 

Branimir Lambov commented on CASSANDRA-17164:
---------------------------------------------

What do you think of applying the following simplifications:
 - The {{promised}} ballot number to be updated whenever a proposal or commit 
with higher ballot number is received by a replica.
Every time we use the promised number we compute it as the max of the three 
values – why not just store that instead?
 - Storing and sending only the higher-ballot value of the "committed" and 
"accepted" registers, with a flag that identifies if the value has been 
committed or only accepted.
The decisions that a proposer makes are taken based on the maximum ballot 
number among "committed" and "accepted", and we only proceed using the newer of 
the two (except in the case of newer empty accepted proposal, where we may 
decide to distribute a commit which can already be shown to have been committed 
to a quorum of replicas).

> 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]

Reply via email to