Unassigned replication shards on elasticSearch 5.2[is it a bug?]

Elastic Stack Elasticsearch
22

I see this in the logs just before some other messages about disconnections:

[2019-03-21T08:00:55,999][WARN ][o.e.t.n.Netty4Transport  ] [node1-100.107.135.3] exception caught on transport layer [[id: 0x18f1e218, L:/100.107.135.3:64102 - R:10.226.137.176/10.226.137.176:9400]], closing connec
java.lang.ClassCastException: null

I don't think this should be happening. However I've searched for an issue like this and cannot find anything that matches. The lack of a proper error message and stack trace is an obstacle, and is caused by running with the JVM option OmitStackTraceInFastThrow which was the default prior to 6.0. Could you add

-XX:-OmitStackTraceInFastThrow

to the config/jvm.options file on every node and perform a rolling restart? Unfortunately this will allocate primaries etc elsewhere so the problem might go away, but hopefully it won't and then we can see more context about that exception.

23

Thanks for your patient.Yes the primary also tried other replication node,It always failed.so you can see the other failed log of other ip.

And thanks for you advice for the jvm option,but I can not rolling restart in a few days,because the application is providing service for the public.I will add it in next maintenance time. then I will reply this topic.

Thank you very much.

1 Like
24

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.