Skip to content

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).

Depends on #12753.

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

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
Collaborator

Yes, we can wait for #12753.

@michaelklishin michaelklishin changed the title Use local read to check node is in maintenance Depends on #12753: Use local read to check node is in maintenance Mar 27, 2025
@michaelklishin
Copy link
Collaborator

This should no longer be necessary with Khepri 0.17.x.

Per discussion with @acogoluegnes @kjnilsson.

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.

3 participants