[
https://issues.apache.org/jira/browse/CASSANDRA-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479183#comment-17479183
]
Benedict Elliott Smith commented on CASSANDRA-17164:
----------------------------------------------------
{quote}Specifically, what stops the following from happening?{quote}
In this example, I believe (3) would not yield {{FOUND_INCOMPLETE_COMMIT}} but
{{FOUND_INCOMPLETE_ACCEPTED}} and so would correctly re-propose (2), expending
its ballot?
{quote}It seems the next prepare will return FOUND_INCOMPLETE_ACCEPTED and
trigger reproposal and commit{quote}
{{hasInProgressProposal}} first checks if {{latestAccepted.update.isEmpty()}}
and if so, returns false, i.e. this would not be considered an incomplete
proposal.
The fast read optimisation does however leave an incomplete _promise_ that we
might want to change to asynchronously send an empty proposal.
> 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]
