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.

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

Backport of #12716 avoid returning stale describeACL responses #15437

Conversation

graphcareful
Copy link
Contributor

@graphcareful graphcareful commented Dec 13, 2023

Backport of #12716

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v23.2.x
  • v23.1.x
  • v22.3.x

Release Notes

Improvements

  • Modifications to avoid stale responses returned from DescribeACLs requests

- When handling this request the responding broker must be the current
leader and will return the last_committed offset within its respective
controller log.

- This offset represents the highest command that has been completely
processed by the controller log.
- This routine will, contact the leader for the last_committed offset
within the controller log, then wait for its local stm to have caught up
until at least that point.
- Before handling describe ACLs requests, ensure that if this node is a
follower, its processing of controller commands has caught up with the
leaders at the point in time the request was recieved.
- This raises the election timeout to 10s while network partitioning a
leader then making a describeACLs request.

- In this scenario any node that is queried should be reporting that
stale results may be returned. Previous followers will be reporting this
because they cannot reach the leader, and the stale leader will be
reporting this because it cannot inject a barrier since it had been
network partitioned.
Copy link
Member

@oleiman oleiman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@piyushredpanda piyushredpanda merged commit 3a369eb into redpanda-data:v23.2.x Dec 13, 2023
26 checks passed
@piyushredpanda piyushredpanda modified the milestones: v23.2.x-next, v23.2.19 Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants