-
Notifications
You must be signed in to change notification settings - Fork 775
Add blog post about Khepri being/becoming the default metadata store. #2298
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
Draft
MirahImage
wants to merge
2
commits into
main
Choose a base branch
from
khepri-default
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
--- | ||
title: "The Roadmap for Making Khepri the Default Metadata Store in RabbitMQ" | ||
tags: ["khepri"] | ||
authors: [mgary] | ||
--- | ||
|
||
Khepri, the new Raft-based RabbitMQ [metadata store](https://www.rabbitmq.com/docs/metadata-store), became fully supported with RabbitMQ 4.0. | ||
Starting with the next release series, RabbitMQ 4.2, we consider Khepri to be mature enough to become the default metadata store, | ||
especially given its substantial data safety and recovery improvements over Mnesia. | ||
|
||
We have performed [a number of benchmarks](#khepri-performance-improvements), showing significant performance improvements in many metadata operations. | ||
|
||
<!-- truncate --> | ||
|
||
## Khepri Feature Flag now stable | ||
|
||
The `khepri_db` feature flag has now been upgraded to `Stable`, meaning it will now be enabled when running the command `rabbitmqctl enable_feature_flag all`, | ||
which should be done after every successful version upgrade. | ||
|
||
Starting with version 4.2, all RabbitMQ clusters will be strongly recommended to adopt Khepri by enabling the `khepri_db` feature flag. This feature flag will | ||
**likely become mandatory** for upgrading from 4.2 onwards. | ||
|
||
While the final decision depends on the community feedback, we expect that starting with RabbitMQ 4.3, | ||
the `khepri_db` feature flag will [graduate](https://www.rabbitmq.com/docs/feature-flags#graduation) to be `Required`. | ||
|
||
### Feature Flag Subsystem | ||
|
||
The RabbitMQ [feature flag subsystem](https://www.rabbitmq.com/docs/feature-flags) was recently improved by introducing a new category of feature flags known as `Soft Required`. | ||
If a feature flag is `Soft Required` starting from version `N`, it is automatically enabled once all RabbitMQ nodes are upgraded to version `N` of RabbitMQ. | ||
This is a change from the previous behavior of `Required`, where a feature flag that became required in version `N` of RabbitMQ must be enabled before upgrading to version `N`. | ||
|
||
It remains best practice to enable feature flags as soon as they become `Stable`, generally immediately after a successful upgrade by running the command `rabbitmqctl enable_feature_flag all`. | ||
Nonetheless, we view the introduction of `Soft Required` feature flags as an improvement in user experience, | ||
as any required feature flags not already enabled will be automatically enabled when required. | ||
|
||
## Khepri Performance Improvements | ||
|
||
The benchmarks below were performed on a 3 node cluster running on Kubernetes | ||
|
||
### 1000 queues, each with 100 bindings | ||
| benchmark | mnesia | khepri | | ||
| -------------------------- | ------ | ------ | | ||
| import | 446 s | 51 s | | ||
| re-import | 16 s | 46 s | | ||
| stop_app | 1.6 s | 1.7 s | | ||
| start_app | 22 s | 4.3 s | | ||
| rolling cluster restart | 108 s | 67 s | | ||
| mnesia to khepri migration | 12.7 s | | | ||
|
||
### 1000 Vhosts | ||
| benchmark | mnesia | khepri | | ||
| -------------------------- | ------ | ------ | | ||
| import | 284 s | 21 s | | ||
| re-import | 2.2 s | 2.2 s | | ||
| stop_app | 2.6 s | 2.4 s | | ||
| start_app | 419 s | 16 s | | ||
| rolling cluster restart | 1447 s | 106 s | | ||
| mnesia to khepri migration | 5.5 s | | | ||
|
||
### 100,000 Classic Queues | ||
| benchmark | mnesia | khepri | | ||
| -------------------------- | ------ | ------ | | ||
| import | 76 s | 76 s | | ||
| re-import | 5.4 s | 5.3 s | | ||
| stop_app | 13 s | 6 s | | ||
| start_app | 26 s | 40 s | | ||
| rolling cluster restart | 185 s | 307 s | | ||
| mnesia to khepri migration | 9.7 s | | | ||
|
||
### 10,000 Quorum Queues | ||
| benchmark | mnesia | khepri | | ||
| -------------------------- | ------ | ------ | | ||
| import | 49 s | 46 s | | ||
| re-import | 1.9 s | 1.8 s | | ||
| stop_app | 1.9 s | 1.7 s | | ||
| start_app | 44 s | 44 s | | ||
| rolling cluster restart | 285 s | 267 s | | ||
| mnesia to khepri migration | 4.7 s | | | ||
|
||
### 1,000 Streams | ||
| benchmark | mnesia | khepri | | ||
| -------------------------- | ------ | ------ | | ||
| import | 3.5 s | 1.2 s | | ||
| re-import | 1.6 s | 1.2 s | | ||
| stop_app | 1.9 s | 1.2 s | | ||
| start_app | 2.5 s | 2.3 s | | ||
| rolling cluster restart | 56 s | 55 s | | ||
| mnesia to khepri migration | 5 s | | |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.