Replies: 2 comments 6 replies
-
|
@JJCella we need a way to reproduce this behavior. A standard list of Mnesia tables in a directory is not something we can work with. We do not even have any details on the history of this node (from what version it was upgraded, when the feature flags were enabled, whether definitions can be imported concurrently, and so on). To my knowledge you are the only one reporting a Mnesia to Khepri migration error in close to a couple of years. @yrigaudeau @MaximeDametis @TomDugue @DamienVicet @suromain @kukinsula FYI, our team really does not appreciate upvoting fests. An hour old issue without any details or prior reports has six reactions. Yeah, right, no doubt that's six different users. Put that energy into helping the maintainers of a tool you almost certainly get for free, release after release, by providing a way to reproduce this migration failure. |
Beta Was this translation helpful? Give feedback.
-
|
We do not guess in this community but we have nothing to work with, so here is one hypothesis I have. It can be that Mnesia was syncing its tables after a rolling node restart and at that moment, the So Mnesia was temporarily missing some tables or table rows, and the migration library has spotted the missing rows. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
When enabling stable feature flags on rabbitmq 4.2.0, mnesia to khepri migration fail with "Tab copier iteration failed" "pattern_matches_no_nodes" error
The error details says that the permissions for a user ("token-0539f1ea-c3f5-ddd9-a1d7-8cce2aa4dfb4") do not match any node. This user was deleted a long time ago but still persists in the configuration files
Searching through the node files, references to this user are still found
Reproduction steps
Expected behavior
This user should no longer appear for the migration to proceed normally
Additional context
I tried recreating the user and then deleting it, but the problem persists
Beta Was this translation helpful? Give feedback.
All reactions