It should not be possible right? If you configures client app to have two or more elasticsearch nodes, it should detect if elasticsearch node is down and not use it during indexing/querying.
What client are you using? Jason On Wed, Jan 8, 2014 at 7:48 PM, <nicolas.l...@guardian.co.uk> wrote: > Hi all, > > I have a situation where if a node in our cluster dies (for whatever > reason) the client app experiences a surge in memory usage, full GCs, and > essentially dies. > > I think this is because the client holds on to the connections for a whlie > before realising the node is dead. > > Does this sound possible? And does anyone have tips for how to deal with > this. My thinking so far is: > > 1. More memory > > 2. A circuit-breaker pattern or some such to make sure the app disconnects > quicker when ES is not responding > > But are there ways to configure the ES client to improve the behaviour > here? > > Thanks, > > Nic > > -- > 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 elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/66c393a3-91d9-4314-a38f-e5267390b9b7%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHO4itxsLZW%3Dw%3DNduajpysjTFiK3hgN%3Def--3frWeOCzoFNsCQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
