Weird ES exception

Elastic Stack Elasticsearch
1

Hi everyone,
I've come across a weird ES exception which is happening all the time
around and which made my ES cluster totally unusable.
I'm running ES 0.20.5, as that was the supported version by Logstash at the
time the cluster was built.
Now I'm seeing the following errors in the logs:

https://gist.github.com/milosgajdos83/6549590

Looks like the error is related to 2 shards from the index which was
created like 3 months ago - 19th June.
Has anyone come across this ?
I have read some posts online suggesting having the same JVm installed -
but we DO have them installed with the same version across the whole
cluster:

$ java -version
java version "1.6.0_27"
OpenJDK Runtime Environment (IcedTea6 1.12.5) (6b27-1.12.5-0ubuntu0.12.04.1)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)

Also someone was suggesting setting the index threadpool queue size to -1 -
I have done that too. But none of this has solve anything.
Any help would be appreciated.
Thanks!
M.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

2

The EsRejectedExecutionException happened because the netty channel handler
was overloaded on one node. You are correct, this is an unusual exception
and points to lack of resources. Check how many network
channels/connections you have currently open if this happens again. It may
also have to do with too many file descriptors in use because netty network
handling also uses quite a lot file descriptors.

It is definitely not an issue of the JVM, or the index queue thread pool.

Jörg

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.