[erlang-questions] Distributed application and netsplit

[Rick Pettit]

This seems like a shame, since distributed application gives you 99% of what you need—it just doesn’t handle recovery from the split brain case in the event of a net split.

It doesn’t seem unreasonable to try to do what you are doing, adding some application-specific logic to determine a winning node, and one or more losing nodes, and to programmatically “reset” the losing nodes such that (1) the application is no longer actively running on them, and (2) failover continues to work going forward.

I can understand if distributed application doesn’t do this out of the box, since this isn’t a one-size-fits-all sort of problem, but surely there is some way to accomplish this without rewriting most of distributed application, no?

By the way, not targeting that question at you Karolis, but rather anyone on the list that may be more familiar with distributed application than we are.

-Rick

On Nov 18, 2014, at 3:44 PM, Karolis Petrauskas <k.petrauskas@REDACTED> wrote:

> On Tue, Nov 18, 2014 at 11:32 PM, Raoul Duke <raould@REDACTED> wrote:
>>> Now I have those "funny things".
>> 
>> does that mean
>> 
>>> Note: Maybe distributed OTP applications aren't the right
>>> mechanism for you in these cases.
>> 
>> ?
>> 
>> (not intended as being snarky.)
> 
> I had a hope to avoid that :) The next alternative is to implement
> this functionality in my application, by starting/stopping relevant
> parts of the supervision tree.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions