Michal/mnesia/fix-handling-node-name-as-table-name/otp-19745 #10147
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.
The problem is that mnesia_decision table stores multiple tuple/record types, and the key is on position 2.
What can be stored:
{mnesia_down, Node, Date, Time}
{master_nodes, Tab, Nodes}
-record(decision, {tid, outcome, disc_nodes, ram_nodes}).
{trans_tid, serial, Serial}
If table name is equal to node name, the
{mnesia_down, ...}
and{master_nodes, ...}
can conflict with each other, and{mnesia_down, ...}
can be interpreted as{master_nodes, ...}
causing crash in mnesia.