This looks a a network configuration challenge. You should review your whole network setup. Look at network device config, host names, gateway setup, DNS name resolution, routers/switches (if your ES clusters spans over subnetworks).
If your network setup is not 100% solid, requests over the wire will timeout, fail, hang, etc. ES (not only ES) can not remedy such situations from the inside of an application. You should not blame REST API, with Java API, it would be the same situation. Jörg On Sat, Aug 2, 2014 at 4:46 PM, Chris Rimondi <[email protected]> wrote: > This is going to sound like a bit of a gripe session so I apologize in > advance. There seems to be a lot of instability and ineffectiveness around > using the REST API to make configuration changes. I realize there have been > some issues related to the NPE returns on certain calls. In addition to > those problems (which I believe have been addressed in ES 1.2.x and 1.3.x) > I have found that if the cluster is in anything but a pristine state the > calls simply do not return or error out with a 503 response. > > Activities such as changing the number of replicas on certain indices or > modifying throttle settings almost always return a 503 on a cluster that is > yellow. It is when the cluster is in a degraded state that we need these > calls the most! Also, simple information calls such as /_cat/nodes will > many times not return when the cluster is yellow. Sometimes it appears that > an API call is hanging only to find out that the setting really did take. > > We maintain multiple ES clusters internally and all the tooling we have > built around supporting them simply assumes the acknowledgement returned > from the API calls is unreliable. Can we expect better reliability with the > Java APIs? Is there plans to make the RESTful calls more robust? > > Thanks, > > Chris > > -- > 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/6c44ad78-d699-4ec0-937c-15322914f924%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/6c44ad78-d699-4ec0-937c-15322914f924%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/CAKdsXoEU%2BtvKwO4yxq4050Ne7pYntDjPLRFU%3D6fbO5%2BuANcrVA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
