plan a rabbitmq khepri metadata store migration in preparation for mnesia removal
domain: rabbitmq.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check the running RabbitMQ version's Khepri status: fully supported but opt-in via the khepri_db feature flag in 4.0 and 4.1, default for new deployments from 4.2, and the only supported metadata store from 4.3 onward.
On a pre-4.2 cluster, explicitly enable the khepri_db feature flag with rabbitmqctl during a maintenance window.
Confirm all nodes in the cluster are upgraded to a version that supports Khepri before enabling the feature flag, since it is cluster-wide and cannot be reverted once enabled.
Watch memory usage during and after migration, since some configuration combinations have been reported to spike memory when the flag is enabled.
After migrating, validate cluster formation, queue and exchange definitions, and any tooling that queried the old store directly, since Khepri's internal data model differs.
Known gotchas
Enabling khepri_db is a one-way feature flag migration; there is no supported downgrade path back to the old metadata store once it's enabled.
Community reports show specific configuration combinations causing out-of-memory conditions during migration; test under representative load in staging first.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?