|
|
| Author |
Message |
|
| jrryjcksn |
 Posted: Tue Jul 05, 2011 3:16 pm |
 |
|
|
Joined: 05 Jul 2011
Posts: 1
Location: Colorado Springs, Colorado
|
Hello,
We have an application running with multiple mnesia nodes possessing disk-based schemas. We see strange behavior when attempting to recover one of the nodes after a disk failure. This only occurs (so far) on one server. We have successfully gone through the recovery process on many other servers many times. After starting the remaining node, we start the failed node on a fresh machine and tell it to connect to the existing mnesia cluster with mnesia:change_config(extra_db_nodes, [<existing node>]). Normally, this causes the recovered node to recreate its schema and then load the tables from the existing node. On the one misbehaving server, some of the tables get loaded from the new node (which has no data) rather than the existing node. With mnesia debugging turned up high, I see the following...
Many messages like:
Mnesia(xxx@host): write performed by {tid,3,<0.178.0>} on record:
and all the tables mentioned in these messages load correctly, followed by:
Mnesia(xxx@host): Create Directory "<our mnesia directory>"
followed by:
Mnesia(xxx@host): write performed by {tid,3,<0.178.0>} on record:
for the "schema" table and then the same messages for all remaining tables. All the tables listed after the "Create Directory" and the schema table end up as "orphaned" tables and get loaded from the new node.
Any insights are much appreciated.
Best regards,
--Jerry Jackson |
|
|
| Back to top |
 
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
