# Shard(s) become assigned when lots of documents are pushed in ES in a short interval of time **URL:** \ **Category:** Elasticsearch\ **Created:** [June 12, 2013, 5:31am UTC](https://discuss.elastic.co/t/shard-s-become-assigned-when-lots-of-documents-are-pushed-in-es-in-a-short-interval-of-time/12367 "2013-06-12T05:31:03Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![amitsoni50](https://avatars.discourse-cdn.com/v4/letter/a/977dab/32.png) [@amitsoni50](https://discuss.elastic.co/u/amitsoni50)\ **Post date:** [June 12, 2013, 5:31am UTC](https://discuss.elastic.co/t/shard-s-become-assigned-when-lots-of-documents-are-pushed-in-es-in-a-short-interval-of-time/12367/1 "2013-06-12T05:31:03Z")
Hi All - I have a two node (each node runs one instance) ES cluster setup and the index has 5 shards with replication enabled (default setting). During the course of my testing, I tried to push lots of documents in ES server and after a while I see that one shard becomes unassigned. I left it in this way for a few hours and the shard was still unassigned. The problem went away after I restarted the ES server. I am able to duplicate this problem and sometimes I see even two shards getting into unassigned status. Any help will be highly appreciated. I have ensured that my two ES servers have the same version and the underlying node has same Java version too. Amit ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:31am UTC](https://discuss.elastic.co/t/shard-s-become-assigned-when-lots-of-documents-are-pushed-in-es-in-a-short-interval-of-time/12367/2 "2017-07-06T02:31:42Z")