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

Bump Khepri from 0.13.0 to 0.14.0 #11247

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Bump Khepri from 0.13.0 to 0.14.0 #11247

wants to merge 3 commits into from

Conversation

dumbbell
Copy link
Member

Release notes:
https://github.com/rabbitmq/khepri/releases/tag/v0.14.0

While here, bump khepri_mnesia_migration from 0.4.0 to 0.5.0 as well.

@dumbbell dumbbell self-assigned this May 16, 2024
dumbbell and others added 3 commits May 17, 2024 14:26
Release notes:
https://github.com/rabbitmq/khepri/releases/tag/v0.14.0

While here, bump khepri_mnesia_migration from 0.4.0 to 0.5.0 as well.
…multiple Khepri SM versions

[Why]
In the context of mixed-version testing, Khepri operations may time out
if one or more Khepri members are running an older version of the state
machine.

[How]
When there are multiple versions of the Khepri state machine being used,
skip specific testcases.
@dumbbell
Copy link
Member Author

Upgrading Khepri is less straightforward than expected, because of the bump of the Khepri state machine version. This highlights two problems during mixed version testing:

  1. A state machine that runs an older state machine version can’t apply commands. This leads to commands timing out.
  2. Local Khepri function references may be invalid on a remote Khepri instance because modules are not the same.

The former is not a bug. This is a behavior inherent to Raft that we need to take into account in the testsuites.

The latter is a known limitation that we started to discuss in rabbitmq/khepri#238 and rabbitmq/khepri#242. We are still studying the issue, nothing is implemented as of this writing.

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

2 participants