# Unassigned shards **URL:** \ **Category:** Elasticsearch\ **Created:** [November 18, 2013, 6:38pm UTC](https://discuss.elastic.co/t/unassigned-shards/14451 "2013-11-18T18:38:00Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Mohamed\_Lrhazi](https://avatars.discourse-cdn.com/v4/letter/m/74df32/32.png) [@Mohamed\_Lrhazi](https://discuss.elastic.co/u/Mohamed_Lrhazi)\ **Post date:** [November 18, 2013, 6:38pm UTC](https://discuss.elastic.co/t/unassigned-shards/14451/1 "2013-11-18T18:38:00Z")
Hello, It seems we over whelmed our 6 node cluster with indexes... we started getting too many open files errors... We added 6 more nodes and also upgraded to the latest version (elasticsearch-0.90.7-1.noarch) Now the cluster starts and loads most shards... except for 58, for which the only log I seem to find is lines like these: [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [el\_2003][11]: not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [de\_2005][10]: not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [de\_2005][4]: not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] What would cause this problem? and how do we recover from it? cluster health: { "cluster\_name" : "foo", "status" : "red", "timed\_out" : false, "number\_of\_nodes" : 13, "number\_of\_data\_nodes" : 12, "active\_primary\_shards" : 4154, "active\_shards" : 8308, "relocating\_shards" : 0, "initializing\_shards" : 0, "unassigned\_shards" : 56 } Thanks a lot, Mohamed. -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Mohamed\_Lrhazi](https://avatars.discourse-cdn.com/v4/letter/m/74df32/32.png) [@Mohamed\_Lrhazi](https://discuss.elastic.co/u/Mohamed_Lrhazi)\ **Post date:** [November 18, 2013, 6:48pm UTC](https://discuss.elastic.co/t/unassigned-shards/14451/2 "2013-11-18T18:48:25Z")
After I pasted the above I notice the number of unassigned shards actually went down to 56, from 58.... maybe it'll keep going down in the next many hours! I'll update this thread in a few hours. Thanks, Mohamed. On Mon, Nov 18, 2013 at 1:38 PM, Mohamed Lrhazi [ml623@georgetown.edu](mailto:ml623@georgetown.edu)wrote: > Hello, > > It seems we over whelmed our 6 node cluster with indexes... we started > getting too many open files errors... > We added 6 more nodes and also upgraded to the latest version > (elasticsearch-0.90.7-1.noarch) > > Now the cluster starts and loads most shards... except for 58, for which > the only log I seem to find is lines like these: > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [el\_2003][11]: > not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [de\_2005][10]: > not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [de\_2005][4]: not > allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] > > What would cause this problem? and how do we recover from it? > > cluster health: > > { > "cluster\_name" : "foo", > "status" : "red", > "timed\_out" : false, > "number\_of\_nodes" : 13, > "number\_of\_data\_nodes" : 12, > "active\_primary\_shards" : 4154, > "active\_shards" : 8308, > "relocating\_shards" : 0, > "initializing\_shards" : 0, > "unassigned\_shards" : 56 > } > > Thanks a lot, > Mohamed. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/0-aw3\_GLVZ0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/0-aw3_GLVZ0/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [November 18, 2013, 10:35pm UTC](https://discuss.elastic.co/t/unassigned-shards/14451/3 "2013-11-18T22:35:48Z")
HI Mohamed, If you get too many open files error you should probably do the following: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html#file-descriptors) Also, the number of shards per node is very high. Unless you know for sure you are not searching all (or many) of them, you can expect CPU issues as they are searched in parallel. Cheers, Boaz On Monday, November 18, 2013 7:48:25 PM UTC+1, Mohamed Lrhazi wrote: > After I pasted the above I notice the number of unassigned shards actually > went down to 56, from 58.... maybe it'll keep going down in the next many > hours! I'll update this thread in a few hours. > > Thanks, > Mohamed. > > On Mon, Nov 18, 2013 at 1:38 PM, Mohamed Lrhazi \ > > > wrote: > > > Hello, > > > > It seems we over whelmed our 6 node cluster with indexes... we started > > getting too many open files errors... > > We added 6 more nodes and also upgraded to the latest version > > (elasticsearch-0.90.7-1.noarch) > > > > Now the cluster starts and loads most shards... except for 58, for which > > the only log I seem to find is lines like these: > > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [el\_2003][11]: > > not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [de\_2005][10]: > > not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [de\_2005][4]: > > not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] > > > > What would cause this problem? and how do we recover from it? > > > > cluster health: > > > > { > > "cluster\_name" : "foo", > > "status" : "red", > > "timed\_out" : false, > > "number\_of\_nodes" : 13, > > "number\_of\_data\_nodes" : 12, > > "active\_primary\_shards" : 4154, > > "active\_shards" : 8308, > > "relocating\_shards" : 0, > > "initializing\_shards" : 0, > > "unassigned\_shards" : 56 > > } > > > > Thanks a lot, > > Mohamed. > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/0-aw3\_GLVZ0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/0-aw3_GLVZ0/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Mohamed\_Lrhazi](https://avatars.discourse-cdn.com/v4/letter/m/74df32/32.png) [@Mohamed\_Lrhazi](https://discuss.elastic.co/u/Mohamed_Lrhazi)\ **Post date:** [November 19, 2013, 2:13pm UTC](https://discuss.elastic.co/t/unassigned-shards/14451/4 "2013-11-19T14:13:49Z")
Thank Boaz. We had increased the allowed max open files and for the moment we do not see that error... We still have unassigned shards though. It seems a colleague of mine was working on the issue too and been deleting indexes that we empty and had unassigned shards.... Could it be that that is the issue, somehow empty, or almost empty (say two documents, while index has 12 shards), indexes fail to get assigned? would that be a known issue? Thanks a lot, Mohamed. On Monday, November 18, 2013 5:35:48 PM UTC-5, Boaz Leskes wrote: > HI Mohamed, > > If you get too many open files error you should probably do the following: > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html#file-descriptors) > > Also, the number of shards per node is very high. Unless you know for sure > you are not searching all (or many) of them, you can expect CPU issues as > they are searched in parallel. > > Cheers, > Boaz > > On Monday, November 18, 2013 7:48:25 PM UTC+1, Mohamed Lrhazi wrote: > > > After I pasted the above I notice the number of unassigned shards > > actually went down to 56, from 58.... maybe it'll keep going down in the > > next many hours! I'll update this thread in a few hours. > > > > Thanks, > > Mohamed. > > > > On Mon, Nov 18, 2013 at 1:38 PM, Mohamed Lrhazi [ml...@georgetown.edu](mailto:ml...@georgetown.edu)wrote: > > > > > Hello, > > > > > > It seems we over whelmed our 6 node cluster with indexes... we started > > > getting too many open files errors... > > > We added 6 more nodes and also upgraded to the latest version > > > (elasticsearch-0.90.7-1.noarch) > > > > > > Now the cluster starts and loads most shards... except for 58, for which > > > the only log I seem to find is lines like these: > > > > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [el\_2003][11]: > > > not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [de\_2005][10]: > > > not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [de\_2005][4]: > > > not allocating, number\_of\_allocated\_shards\_found [0], required\_number [1] > > > > > > What would cause this problem? and how do we recover from it? > > > > > > cluster health: > > > > > > { > > > "cluster\_name" : "foo", > > > "status" : "red", > > > "timed\_out" : false, > > > "number\_of\_nodes" : 13, > > > "number\_of\_data\_nodes" : 12, > > > "active\_primary\_shards" : 4154, > > > "active\_shards" : 8308, > > > "relocating\_shards" : 0, > > > "initializing\_shards" : 0, > > > "unassigned\_shards" : 56 > > > } > > > > > > Thanks a lot, > > > Mohamed. > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/0-aw3\_GLVZ0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/0-aw3_GLVZ0/unsubscribe). > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [November 20, 2013, 10:57am UTC](https://discuss.elastic.co/t/unassigned-shards/14451/5 "2013-11-20T10:57:56Z")
Hi Mohamed, The number of documents in a shard should not effect whether it's assigned or not. When a shard fails too often on a node, ES does not try to allocate that shard on that node anymore. I think what happened is that you have shard allocation failed too often due to the max open files issue and got all the nodes black listed for those shards. Can you try restarting the cluster with th new max open files settings and see if that helps? Cheers, Boaz On Tue, Nov 19, 2013 at 3:13 PM, Mohamed Lrhazi [ml623@georgetown.edu](mailto:ml623@georgetown.edu)wrote: > Thank Boaz. We had increased the allowed max open files and for the moment > we do not see that error... We still have unassigned shards though. It > seems a colleague of mine was working on the issue too and been deleting > indexes that we empty and had unassigned shards.... > > Could it be that that is the issue, somehow empty, or almost empty (say > two documents, while index has 12 shards), indexes fail to get assigned? > would that be a known issue? > > Thanks a lot, > Mohamed. > > On Monday, November 18, 2013 5:35:48 PM UTC-5, Boaz Leskes wrote: > > > HI Mohamed, > > > > If you get too many open files error you should probably do the > > following: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/) > > current/setup-configuration.html#file-descriptors > > > > Also, the number of shards per node is very high. Unless you know for > > sure you are not searching all (or many) of them, you can expect CPU issues > > as they are searched in parallel. > > > > Cheers, > > Boaz > > > > On Monday, November 18, 2013 7:48:25 PM UTC+1, Mohamed Lrhazi wrote: > > > > > After I pasted the above I notice the number of unassigned shards > > > actually went down to 56, from 58.... maybe it'll keep going down in the > > > next many hours! I'll update this thread in a few hours. > > > > > > Thanks, > > > Mohamed. > > > > > > On Mon, Nov 18, 2013 at 1:38 PM, Mohamed Lrhazi [ml...@georgetown.edu](mailto:ml...@georgetown.edu)wrote: > > > > > > > Hello, > > > > > > > > It seems we over whelmed our 6 node cluster with indexes... we started > > > > getting too many open files errors... > > > > We added 6 more nodes and also upgraded to the latest version > > > > (elasticsearch-0.90.7-1.noarch) > > > > > > > > Now the cluster starts and loads most shards... except for 58, for > > > > which the only log I seem to find is lines like these: > > > > > > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] > > > > [el\_2003][11]: not allocating, number\_of\_allocated\_shards\_found [0], > > > > required\_number [1] > > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] > > > > [de\_2005][10]: not allocating, number\_of\_allocated\_shards\_found [0], > > > > required\_number [1] > > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] [de\_2005][4]: > > > > not allocating, number\_of\_allocated\_shards\_found [0], required\_number > > > > [1] > > > > > > > > What would cause this problem? and how do we recover from it? > > > > > > > > cluster health: > > > > > > > > { > > > > "cluster\_name" : "foo", > > > > "status" : "red", > > > > "timed\_out" : false, > > > > "number\_of\_nodes" : 13, > > > > "number\_of\_data\_nodes" : 12, > > > > "active\_primary\_shards" : 4154, > > > > "active\_shards" : 8308, > > > > "relocating\_shards" : 0, > > > > "initializing\_shards" : 0, > > > > "unassigned\_shards" : 56 > > > > } > > > > > > > > Thanks a lot, > > > > Mohamed. > > > > > > > > -- > > > > You received this message because you are subscribed to a topic in the > > > > Google Groups "elasticsearch" group. > > > > To unsubscribe from this topic, visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > topic/elasticsearch/0-aw3\_GLVZ0/unsubscribe. > > > > To unsubscribe from this group and all its topics, send an email to > > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/0-aw3\_GLVZ0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/0-aw3_GLVZ0/unsubscribe). > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Mohamed\_Lrhazi](https://avatars.discourse-cdn.com/v4/letter/m/74df32/32.png) [@Mohamed\_Lrhazi](https://discuss.elastic.co/u/Mohamed_Lrhazi)\ **Post date:** [November 20, 2013, 2:44pm UTC](https://discuss.elastic.co/t/unassigned-shards/14451/6 "2013-11-20T14:44:54Z")
Thanks Boaz, we tried restarting a few times to no avail... but we now just went ahead and deleted the affected indexes and recreated them... Mohamed. On Wed, Nov 20, 2013 at 5:57 AM, Boaz Leskes [b.leskes@gmail.com](mailto:b.leskes@gmail.com) wrote: > Hi Mohamed, > > The number of documents in a shard should not effect whether it's assigned > or not. > > When a shard fails too often on a node, ES does not try to allocate that > shard on that node anymore. I think what happened is that you have shard > allocation failed too often due to the max open files issue and got all the > nodes black listed for those shards. Can you try restarting the cluster > with th new max open files settings and see if that helps? > > Cheers, > Boaz > > On Tue, Nov 19, 2013 at 3:13 PM, Mohamed Lrhazi [ml623@georgetown.edu](mailto:ml623@georgetown.edu)wrote: > > > Thank Boaz. We had increased the allowed max open files and for the > > moment we do not see that error... We still have unassigned shards though. > > It seems a colleague of mine was working on the issue too and been deleting > > indexes that we empty and had unassigned shards.... > > > > Could it be that that is the issue, somehow empty, or almost empty (say > > two documents, while index has 12 shards), indexes fail to get assigned? > > would that be a known issue? > > > > Thanks a lot, > > Mohamed. > > > > On Monday, November 18, 2013 5:35:48 PM UTC-5, Boaz Leskes wrote: > > > > > HI Mohamed, > > > > > > If you get too many open files error you should probably do the > > > following: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/) > > > elasticsearch/reference/current/setup-configuration. > > > html#file-descriptors > > > > > > Also, the number of shards per node is very high. Unless you know for > > > sure you are not searching all (or many) of them, you can expect CPU issues > > > as they are searched in parallel. > > > > > > Cheers, > > > Boaz > > > > > > On Monday, November 18, 2013 7:48:25 PM UTC+1, Mohamed Lrhazi wrote: > > > > > > > After I pasted the above I notice the number of unassigned shards > > > > actually went down to 56, from 58.... maybe it'll keep going down in the > > > > next many hours! I'll update this thread in a few hours. > > > > > > > > Thanks, > > > > Mohamed. > > > > > > > > On Mon, Nov 18, 2013 at 1:38 PM, Mohamed Lrhazi [ml...@georgetown.edu](mailto:ml...@georgetown.edu)wrote: > > > > > > > > > Hello, > > > > > > > > > > It seems we over whelmed our 6 node cluster with indexes... we started > > > > > getting too many open files errors... > > > > > We added 6 more nodes and also upgraded to the latest version > > > > > (elasticsearch-0.90.7-1.noarch) > > > > > > > > > > Now the cluster starts and loads most shards... except for 58, for > > > > > which the only log I seem to find is lines like these: > > > > > > > > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] > > > > > [el\_2003][11]: not allocating, number\_of\_allocated\_shards\_found [0], > > > > > required\_number [1] > > > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] > > > > > [de\_2005][10]: not allocating, number\_of\_allocated\_shards\_found [0], > > > > > required\_number [1] > > > > > [2013-11-18 13:19:27,277][DEBUG][gateway.local] [rap-es] > > > > > [de\_2005][4]: not allocating, number\_of\_allocated\_shards\_found [0], > > > > > required\_number [1] > > > > > > > > > > What would cause this problem? and how do we recover from it? > > > > > > > > > > cluster health: > > > > > > > > > > { > > > > > "cluster\_name" : "foo", > > > > > "status" : "red", > > > > > "timed\_out" : false, > > > > > "number\_of\_nodes" : 13, > > > > > "number\_of\_data\_nodes" : 12, > > > > > "active\_primary\_shards" : 4154, > > > > > "active\_shards" : 8308, > > > > > "relocating\_shards" : 0, > > > > > "initializing\_shards" : 0, > > > > > "unassigned\_shards" : 56 > > > > > } > > > > > > > > > > Thanks a lot, > > > > > Mohamed. > > > > > > > > > > -- > > > > > You received this message because you are subscribed to a topic in the > > > > > Google Groups "elasticsearch" group. > > > > > To unsubscribe from this topic, visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > topic/elasticsearch/0-aw3\_GLVZ0/unsubscribe. > > > > > To unsubscribe from this group and all its topics, send an email to > > > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > > > -- > > > > You received this message because you are subscribed to a topic in the > > > > Google Groups "elasticsearch" group. > > > > To unsubscribe from this topic, visit > > > > [https://groups.google.com/d/topic/elasticsearch/0-aw3\_GLVZ0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/0-aw3_GLVZ0/unsubscribe). > > > > To unsubscribe from this group and all its topics, send an email to > > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/0-aw3\_GLVZ0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/0-aw3_GLVZ0/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:05am UTC](https://discuss.elastic.co/t/unassigned-shards/14451/7 "2017-07-06T02:05:55Z")