Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In <a href="http://erlang.2086793.n4.nabble.com/About-mnesia-in-multi-nodes-td2119396.html" rel="nofollow">this discussion</a> a situation similar to the one you're facing is presented.</p> <p>Reading from that source:</p> <blockquote> <p>At startup Mnesia tries to connect with the other nodes and if that suceeds it loads its tables from them. If the other nodes are down, it looks for mnesia_down marks in its local transaction log in order to determine if it has a consistent replica or not of its tables. The node that was shutdown last has mnesia_down's from all the other nodes. This means that it safely can load its tables. If some of the other nodes where started first (as in your case) Mnesia will wait indefinitely for another node to connect in order to load its tables</p> </blockquote> <p>You're shutting down node 1 first, so it doesn't have the <code>mnesia_down</code> from the other node. What happens if you reverse the shutting down order?</p> <p>Also, it should be possible to force the table loading via the <a href="http://www.erlang.org/doc/man/mnesia.html#force_load_table-1" rel="nofollow">force_load_table/1</a> function:</p> <pre><code>force_load_table(Tab) -&gt; yes | ErrorDescription </code></pre> <blockquote> <p>The Mnesia algorithm for table load might lead to a situation where a table cannot be loaded. This situation occurs when a node is started and Mnesia concludes, or suspects, that another copy of the table was active after this local copy became inactive due to a system crash.</p> <p>If this situation is not acceptable, this function can be used to override the strategy of the Mnesia table load algorithm. This could lead to a situation where some transaction effects are lost with a inconsistent database as result, but for some applications high availability is more important than consistent data.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POquestion about mnesia distribution
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRoberto Aloi
    1. USRoberto Aloi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POquestion about mnesia distribution
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COthanks, that partly solves my problem. but supposed i started node 1 using mnesia:force_load_table/1, and after that i found node 2 is up again, is there a way to merge the changes? mnesia:set_master_node seems to work during startup, but cannot be used to force a "fetch" from the master node.
      singulars
      1. PO
      1. USChi Zhang
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload