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

Use local read to check node is in maintenance #13172

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

acogoluegnes
Copy link
Contributor

@acogoluegnes acogoluegnes commented Jan 29, 2025

In stream reader. The consistent read may cause some timeout for the metadata frame (when Khepri is used as the data store).

In stream reader. The consistent read may cause some timeout for the
metadata frame.
@michaelklishin
Copy link
Member

A local read should be perfectly sufficient in this case.

@acogoluegnes
Copy link
Contributor Author

It is likely to be due to the version mismatch between Khepri and RA (we upgraded RA to 2.16 in RabbitMQ, but Khepri is not fully compatible with it). I agree the stream plugin could use a local read in this case, even though the metadata frame can be used when there is instability in the cluster (client applications recovering their connection during a rolling upgrade/restart).

Maybe we should wait for #12753 to be merged and make sure it fixes the flake before changing the stream plugin to use a local read.

@michaelklishin
Copy link
Member

Yes, we can wait for #12753.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants