The client may hang because I assume the cluster state got unavailable, and minimum master condition is no longer met. If you re-add the failed node, the cluster state will be available again, and I think the client will continue.
Jörg On Sun, Nov 30, 2014 at 11:07 PM, <[email protected]> wrote: > > 2 nodes are not enough to form a distributed system, such a cluster is >> prone to split brains, because there is no algorithm that can decide what >> node shall continue as master in case of a single node failure. >> > > Agreed! > > >> ES has come precautions built in to suspend execution in this case. >> >> Please use at least 3 nodes and an odd number of nodes with explicit >> minimum_master_nodes setting for better split brain prevention. >> > > Okay! But what about the connectivity issue which started this thread? The > client application still hangs and a client restart seems to solve the > issue. There is no cluster state change when restarting app, isn't it? > > Markus > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/430017aa-7c0e-4550-b00e-05040d2e73b2%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/430017aa-7c0e-4550-b00e-05040d2e73b2%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGxVWXv7DUg1ZjO8duG04kgrzyrRnq8rAp9__cG%2Bj1UVw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
