Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

raft: reject linearizable_barrier if not is_leader() #10921

Merged
merged 1 commit into from
May 24, 2023
Merged

raft: reject linearizable_barrier if not is_leader() #10921

merged 1 commit into from
May 24, 2023

Commits on May 22, 2023

  1. raft: reject linearizable_barrier if not is_leader() 

    A test noticed that a Kafka ListOffsets request issued
concurrently with raft election could return a commit_index
lower than the last message committed on the previous leader.

To the client this looks like time travel on their topic's HWM.

We could special case this for ListOffsets, but linearizable_barrier
is used lots of places, and probably none of them actually want to run
in this brief millisecond between leader election and is_leader()
becoming true.

Fixes redpanda-data#10885
    @jcsp
    jcsp committed May 22, 2023
    Configuration menu
    Copy the full SHA
    d170fc6 View commit details
    Browse the repository at this point in the history