# Shards become unallocated during indexing **URL:** \ **Category:** Elasticsearch\ **Created:** [April 29, 2014, 2:02pm UTC](https://discuss.elastic.co/t/shards-become-unallocated-during-indexing/17263 "2014-04-29T14:02:03Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Sviatoslav\_Abakumov](https://avatars.discourse-cdn.com/v4/letter/s/fbc32d/32.png) [@Sviatoslav\_Abakumov](https://discuss.elastic.co/u/Sviatoslav_Abakumov)\ **Post date:** [April 29, 2014, 2:02pm UTC](https://discuss.elastic.co/t/shards-become-unallocated-during-indexing/17263/1 "2014-04-29T14:02:03Z")
Hello, I have a 40-shard index, currently its size is 39 GB. There's only one type in the index, and one of the fields is of nested type that holds complex documents. When I start to populate the index further, after adding about 3000 documents server becomes unavailable for some time. Then it becomes available again, but one of the shards is left unallocated. After I restart ES, all shards load just fine, but the story repeats itself. Thanks. -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/e471d7af-65db-44ec-9fc1-00af68f6f4d4%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e471d7af-65db-44ec-9fc1-00af68f6f4d4%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [May 5, 2014, 10:22am UTC](https://discuss.elastic.co/t/shards-become-unallocated-during-indexing/17263/2 "2014-05-05T10:22:12Z")
Hey, this is very hard to tell without further debugging/information. Can you check your logfiles, if there are any exceptions popping up? Can you check the logfile of your master node, if node joins/leaves or even master elections happen? Also you should add monitoring to your infrastructure (like Marvel) in order to find out more about your running system... --Alex On Tue, Apr 29, 2014 at 4:02 PM, Sviatoslav Abakumov \< [abakumov.sviatoslav@progforce.com](mailto:abakumov.sviatoslav@progforce.com)\> wrote: > Hello, > > I have a 40-shard index, currently its size is 39 GB. There's only one > type in the index, and one of the fields is of nested type that holds > complex documents. > When I start to populate the index further, after adding about 3000 > documents server becomes unavailable for some time. Then it becomes > available again, but one of the shards is left unallocated. > After I restart ES, all shards load just fine, but the story repeats > itself. > > Thanks. > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/e471d7af-65db-44ec-9fc1-00af68f6f4d4%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e471d7af-65db-44ec-9fc1-00af68f6f4d4%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/e471d7af-65db-44ec-9fc1-00af68f6f4d4%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e471d7af-65db-44ec-9fc1-00af68f6f4d4%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGCwEM\_XpDde6-R8D210pRBSCDQNeVrngBN\_h%3DtVyptQt89b1A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM_XpDde6-R8D210pRBSCDQNeVrngBN_h%3DtVyptQt89b1A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:31am UTC](https://discuss.elastic.co/t/shards-become-unallocated-during-indexing/17263/3 "2017-07-06T01:31:45Z")
Closed on July 6, 2017, 1:31am UTC