I believe the problem comes from the fact that the index does not exists (or its a "blocked" meta data state, where we don't know which indices we have), and then the create index API is executed with its own timeout instead of using the index request timeout. I fixed it in master: https://github.com/elasticsearch/elasticsearch/issues/1664.
On Wednesday, February 1, 2012 at 1:54 PM, inflynx wrote:
I am tring to increase the timeout for the shard with little luck.
The default value is [1m], which I'd like to increase to [3m] as follows:
String json = marshaller.write(entity);
However, ElasticSearch does not seem to pick up the change and times out on
Is there anything else that I may be missing?
Thanks so much!
View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Shard-Timeout-tp3706354p3706354.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com (http://Nabble.com).