Re: Non-overlapping Application Distribution Node Sets

Henrik,

Yes, I haven't forgotten about this.  It will get the required attention
in the next few weeks.

-- 
	-Vance

On Mon, Feb 17, 2014 at 10:00:06AM +0100, Henrik Nord wrote:
}  Ping!
}  
}  
}  
}  On 2013-06-19 16:01, Siri Hansen wrote:
}  >Hi Vance,
}  >
}  >we have decided that we would like to take in this functionality
}  >if the bug I mentioned in my last mail is corrected and some more
}  >extensive tests are added. We also need an update of the
}  >documentation, of course.
}  >
}  >Thanks for your contribution!
}  >/siri
}  >
}  >
}  >2013/6/14 Vance Shipley <[email protected] <mailto:[email protected]>>
}  >
}  >    On Thu, Jun 13, 2013 at 02:46:38PM +0530, Vance Shipley wrote:
}  >    }  The use case is simply that we run the same application on each
}  >    node in
}  >    }  a distributed Erlang cluster and want to designate a standby
}  >    node for
}  >    }  each as depicted below:
}  >
}  >    Siri,
}  >
}  >    For further clarification I should add that the node pairs need to
}  >    know about each other because they use distributed mnesia.  The node
}  >    pairs which may run an instance of an application each maintain a copy
}  >    of the mnesia tables which they need to run.  If serverA fails node2
}  >    will take over it's app1 instance and continue operation with the
}  >    current
}  >    tables.  The problem comes in with the fact that the active nodes all
}  >    use mnesia distribution and pg2 betwen them (e.g. node & node4) as
}  >    well.
}  >
}  >    --
}  >            -Vance
}  >
}  >
}  >
}  >
}  >_______________________________________________
}  >erlang-patches mailing list
}  >[email protected]
}  >http://erlang.org/mailman/listinfo/erlang-patches
}  
}  -- 
}  /Henrik Nord Erlang/OTP
}  

-- 
	-Vance
_______________________________________________
erlang-patches mailing list
[email protected]
http://erlang.org/mailman/listinfo/erlang-patches