[
https://issues.apache.org/jira/browse/CASSANDRA-17162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445931#comment-17445931
]
Unmesh Joshi commented on CASSANDRA-17162:
------------------------------------------
Ah, I missed the USING TIMESTAMP part of the proposal update queries. So even
if the updates are accepted, stale value will never overwrite the newer
proposal because of USING timestamp part of the query.
I see that a subsequent Prepare call returns the accepted commit with higher
timestamp ballot.
> In the paxos implementation, a delayed proposal might overwrite newer values
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-17162
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17162
> Project: Cassandra
> Issue Type: Bug
> Reporter: Unmesh Joshi
> Priority: Normal
> Attachments: paxos-fix.patch
>
>
> I was going through this blog post , which talks about a possible bug in
> paxos implementation if in-progress ballot is not set while accepting a
> proposal.
> [https://brooker.co.za/blog/2021/11/16/paxos.html]
> I tried writing a failing test and possible fix.
> The in_progress_ballot needs to be set when accepting a proposal. The current
> implementation sets only the proposal_ballot when accepting a proposal.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
