[erlang-questions] Question about distributed mnesia behavior

[cao.xu]

Thanks very much. I got it.

On 2012-4-28, at 下午6:39, Joseph Norton wrote:

> Yes, it is expected behavior.
> 
> See this section in the Mnesia user's guide:
> 
> At start-up, it must be noted that all tables residing on nodes without a mnesia_down entry, may have fresher replicas. Their replicas may have been updated after the termination of Mnesia on the current node. In order to catch up with the latest updates, transfer a copy of the table from one of these other "fresh" nodes. If you are unlucky, other nodes may be down and you must wait for the table to be loaded on one of these nodes before receiving a fresh copy of the table.
> 
> http://www.erlang.org/doc/apps/mnesia/Mnesia_chap7.html#id78236
> 
> On 2012/04/28, at 19:16, "cao.xu" <cao.xu@REDACTED> wrote:
> 
>> Yes. It is accessible as you expect. Does that mean the shutdown order affect the result of single restart, why?
>> 
>> Xu Cao
>> 
>> On 2012-4-28, at 下午5:41, Joseph Norton wrote:
>> 
>>> Can you repeat your test and make sure to shutdown test1 AFTER test2? 
>>> 
>>> If you then restart test1 first, is the 'test' table accessible on test1?
>>> 
>>> Joe N.
>>> 
>>> 
>>> 
>>> On 2012/04/28, at 17:40, "cao.xu" <cao.xu@REDACTED> wrote:
>>> 
>>>> Then I shutdown these two nodes and restarted 'test2', the table 'test' was still accessible and I could read and write on it.  But when I shutdown 'test2' and restarted 'test1', the table 'test' was unaccessible.
>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120428/bc9bba35/attachment.htm>