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

**URL:** <https://discuss.elastic.co/t/unassigned-replication-shards-on-elasticsearch-5-2-is-it-a-bug/173459>\
**Category:** Elasticsearch\
**Created:** [March 22, 2019, 9:12am UTC](https://discuss.elastic.co/t/unassigned-replication-shards-on-elasticsearch-5-2-is-it-a-bug/173459 "2019-03-22T09:12:46Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 25, 2019, 9:27am UTC](https://discuss.elastic.co/t/unassigned-replication-shards-on-elasticsearch-5-2-is-it-a-bug/173459/22 "2019-03-25T09:27:08Z")

</div>

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

```nohighlight
[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](https://github.com/elastic/elasticsearch/pull/24426). Could you add

```auto
-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.

---

<div class="post-metadata">

**Author:** ![Adminstrator](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adminstrator/32/42575_2.png) [@Adminstrator](https://discuss.elastic.co/u/Adminstrator)\
**Post date:** [March 25, 2019, 10:06am UTC](https://discuss.elastic.co/t/unassigned-replication-shards-on-elasticsearch-5-2-is-it-a-bug/173459/23 "2019-03-25T10:06:30Z")

</div>

> [@DavidTurner](#):
>
> I see this in the logs just before some other messages about disconnections:

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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 22, 2019, 10:06am UTC](https://discuss.elastic.co/t/unassigned-replication-shards-on-elasticsearch-5-2-is-it-a-bug/173459/24 "2019-04-22T10:06:34Z")

</div>

Closed on April 22, 2019, 10:06am UTC

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

[Previous page](https://discuss.elastic.co/t/unassigned-replication-shards-on-elasticsearch-5-2-is-it-a-bug/173459.md?page=1)