We have 20 node ES 90.2 cluster with about 8mil documents. We use pyes for
talking to elasticsearch. We are using 4 primary 1 replica shard setting
for each index creation.
We have a timeout value of 2 (obviously low) seconds every time we try to
create an index we are getting an IndexAlreadyExistException even though
the index doesn't exist. Looks like it is thrown ES itself with the
following exception
string:
'{"error":"RemoteTransportException[[Tempest][inet[/10.3.190.87:9300]][indices/create]];
nested: IndexAlreadyExistsException[[088c058862a240a0b58a883caf0ef69a]
Already exists]; ","status":400}'
And when we set the timeout to something larger like 5 seconds we don't see
this exception.
Any reason why ES throws an cryptic IndexAlreadyExists exception for
transport timeouts?
And what is a reasonable timeout to set for Elastic search operations?
--
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/b04a1c3f-264d-4f9b-a996-8a92f8b5eb4e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
