Node failing with a schema_integrity_check_failed after successful Khepri migration (4.1 to 4.2)
#16041
-
Describe the bugI am upgrading my RabbitMQ cluster from 4.1 to 4.2 (running on Erlang 27). I am experiencing a persistent boot failure on nodes after enabling Khepri. When I restart the one of the cluster node, it was get error. Reproduction steps
rabbit-config.txt Expected behaviorI want to restart nodes without any error. Additional contextI can not upgrade my environment because of this error. I try to delete all data and restart docker containers with 4.2.0, enabled khepri. But it didn't work. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
@skry-dev according to the error, something in your cluster still requires Mnesia but it is, well, not started any more since you have migrated to Khepri. This is almost certainly a 3rd party plugin and not something in RabbitMQ. Neither your The latter was updated to start Mnesia separately but then archived. That's all we can suggest given the amount of information you have shared. Also, the most recent RabbitMQ |
Beta Was this translation helpful? Give feedback.
@skry-dev that plugin was updated to start Mnesia, so you probably also run an old version.
That said, that plugin is no longer maintained, so you should move away from it in general.