# \[Shard Unassigned\] Solutions to reassigned the shard
**URL:** https://discuss.elastic.co/t/shard-unassigned-solutions-to-reassigned-the-shard/19163
**Category:** Elasticsearch
**Created:** [August 8, 2014, 1:17pm UTC](https://discuss.elastic.co/t/shard-unassigned-solutions-to-reassigned-the-shard/19163 "2014-08-08T13:17:57Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@AlexK](https://discuss.elastic.co/u/AlexK)
#### Post date: [August 8, 2014, 1:17pm UTC](https://discuss.elastic.co/t/shard-unassigned-solutions-to-reassigned-the-shard/19163/1 "2014-08-08T13:17:57Z")
Hi,
I am using ElasticSearch 1.2.0.
I have a question about the solution to solve the "Shard unassigned"
problem.
Here my setup, pretty simple:
1 NODE - 2 SHARDS / index - NO REPLICA
The situation is the following:
- I manually moved all the content of _/var/data/elasticsearc_h to another
location for backup need;
So I am able to start with a fresh cluster.
- I restarted the service and everything was going fine until I realised
that all my _Kibana dashboards were not available_ on the newly live
cluster.
I understood it was because of the previous move of the files, so I
simply moved the\* kibana-int\* index directory from the backup dir back to
_/var/data/elasticsearch_
If it was so simple...🙂
The new cluster showed the old _kibana-int_ index as unassigned despite
restart of the service.
Questions:
- How the new cluster can unassigned this index (does it see that it does
not created this index itself based on timestamp or other, and therefore
decide to not take it...) ?
- How can I assign this index ? The only solution I know is to start
another node (so a 2 nodes cluster) hoping that the second node will take
the\* kibana-int \*and then move this index onto the first node.
Thanks a lot for sharing your experience on this matters, I am sure it will
help other.
Best Regards,
Alex
--
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/2fce0328-56f2-4a6c-9343-c4808e983549%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2fce0328-56f2-4a6c-9343-c4808e983549%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [August 9, 2014, 12:23am UTC](https://discuss.elastic.co/t/shard-unassigned-solutions-to-reassigned-the-shard/19163/2 "2014-08-09T00:23:32Z")
It's probably because the cluster state doesn't know about the index even
though it can see it on the filesystem.
I don't know if you can recover this, but there might be a way someone can
suggest.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
On 8 August 2014 23:17, AlexK [alexandre.kapell@gmail.com](mailto:alexandre.kapell@gmail.com) wrote:
> Hi,
>
> I am using Elasticsearch 1.2.0.
>
> I have a question about the solution to solve the "Shard unassigned"
> problem.
>
> Here my setup, pretty simple:
> 1 NODE - 2 SHARDS / index - NO REPLICA
>
> The situation is the following:
>
> - I manually moved all the content of _/var/data/elasticsearc_h to
> another location for backup need;
> So I am able to start with a fresh cluster.
> - I restarted the service and everything was going fine until I realised
> that all my _Kibana dashboards were not available_ on the newly live
> cluster.
> I understood it was because of the previous move of the files, so I
> simply moved the\* kibana-int\* index directory from the backup dir back to
> _/var/data/elasticsearch_
>
> If it was so simple...🙂
> The new cluster showed the old _kibana-int_ index as unassigned despite
> restart of the service.
>
> Questions:
>
> - How the new cluster can unassigned this index (does it see that it does
> not created this index itself based on timestamp or other, and therefore
> decide to not take it...) ?
> - How can I assign this index ? The only solution I know is to start
> another node (so a 2 nodes cluster) hoping that the second node will take
> the\* kibana-int \*and then move this index onto the first node.
>
> Thanks a lot for sharing your experience on this matters, I am sure it
> will help other.
>
> Best Regards,
> Alex
>
> --
> 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/2fce0328-56f2-4a6c-9343-c4808e983549%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2fce0328-56f2-4a6c-9343-c4808e983549%40googlegroups.com)
> [https://groups.google.com/d/msgid/elasticsearch/2fce0328-56f2-4a6c-9343-c4808e983549%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/2fce0328-56f2-4a6c-9343-c4808e983549%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/CAEM624YT8Zz8o901z6RMFdR\_mMYwvOhc6FSkTM%2BghLJ2zJa0\_w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YT8Zz8o901z6RMFdR_mMYwvOhc6FSkTM%2BghLJ2zJa0_w%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@AlexK](https://discuss.elastic.co/u/AlexK)
#### Post date: [August 11, 2014, 5:10pm UTC](https://discuss.elastic.co/t/shard-unassigned-solutions-to-reassigned-the-shard/19163/3 "2014-08-11T17:10:47Z")
Yeah, I agree.
It is kind of frustrating, as I know it is on the right place but ES gives
me still YELLOW !
I wish It was only a matter of modifying a single file in the index
directory.
Can someone share its experience on the matter ?
Thanks,
Alex.
2014-08-09 2:23 GMT+02:00 Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com):
> It's probably because the cluster state doesn't know about the index even
> though it can see it on the filesystem.
> I don't know if you can recover this, but there might be a way someone can
> suggest.
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)
> web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
>
> On 8 August 2014 23:17, AlexK [alexandre.kapell@gmail.com](mailto:alexandre.kapell@gmail.com) wrote:
>
> > Hi,
> >
> > I am using Elasticsearch 1.2.0.
> >
> > I have a question about the solution to solve the "Shard unassigned"
> > problem.
> >
> > Here my setup, pretty simple:
> > 1 NODE - 2 SHARDS / index - NO REPLICA
> >
> > The situation is the following:
> >
> > - I manually moved all the content of _/var/data/elasticsearc_h to
> > another location for backup need;
> > So I am able to start with a fresh cluster.
> > - I restarted the service and everything was going fine until I realised
> > that all my _Kibana dashboards were not available_ on the newly live
> > cluster.
> > I understood it was because of the previous move of the files, so I
> > simply moved the\* kibana-int\* index directory from the backup dir back
> > to _/var/data/elasticsearch_
> >
> > If it was so simple...🙂
> > The new cluster showed the old _kibana-int_ index as unassigned despite
> > restart of the service.
> >
> > Questions:
> >
> > - How the new cluster can unassigned this index (does it see that it
> > does not created this index itself based on timestamp or other, and
> > therefore decide to not take it...) ?
> > - How can I assign this index ? The only solution I know is to start
> > another node (so a 2 nodes cluster) hoping that the second node will take
> > the\* kibana-int \*and then move this index onto the first node.
> >
> > Thanks a lot for sharing your experience on this matters, I am sure it
> > will help other.
> >
> > Best Regards,
> > Alex
> >
> > --
> > 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/2fce0328-56f2-4a6c-9343-c4808e983549%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2fce0328-56f2-4a6c-9343-c4808e983549%40googlegroups.com)
> > [https://groups.google.com/d/msgid/elasticsearch/2fce0328-56f2-4a6c-9343-c4808e983549%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/2fce0328-56f2-4a6c-9343-c4808e983549%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 a topic in the
> Google Groups "elasticsearch" group.
> To unsubscribe from this topic, visit
> [https://groups.google.com/d/topic/elasticsearch/7elBE7EUYmI/unsubscribe](https://groups.google.com/d/topic/elasticsearch/7elBE7EUYmI/unsubscribe).
> To unsubscribe from this group and all its topics, 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/CAEM624YT8Zz8o901z6RMFdR\_mMYwvOhc6FSkTM%2BghLJ2zJa0\_w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YT8Zz8o901z6RMFdR_mMYwvOhc6FSkTM%2BghLJ2zJa0_w%40mail.gmail.com)
> [https://groups.google.com/d/msgid/elasticsearch/CAEM624YT8Zz8o901z6RMFdR\_mMYwvOhc6FSkTM%2BghLJ2zJa0\_w%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624YT8Zz8o901z6RMFdR_mMYwvOhc6FSkTM%2BghLJ2zJa0_w%40mail.gmail.com?utm_medium=email&utm_source=footer)
> .
>
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
Alexandre KAPELL
Email : [alexandre.kapell@gmail.com](mailto:alexandre.kapell@gmail.com)
Tél : (+33) 06.37.67.04.03
--
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/CAGYBOpnDf%2BF0jzTTtjbo9\_xaQ5NKHFku%3DOQvpJ30NPDUBzb1Dw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGYBOpnDf%2BF0jzTTtjbo9_xaQ5NKHFku%3DOQvpJ30NPDUBzb1Dw%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@AlexK](https://discuss.elastic.co/u/AlexK)
#### Post date: [August 28, 2014, 5:24pm UTC](https://discuss.elastic.co/t/shard-unassigned-solutions-to-reassigned-the-shard/19163/4 "2014-08-28T17:24:34Z")
Hi,
Does anyone has a definitive answer to this problem ?
Alex.
Le lundi 11 août 2014 19:11:02 UTC+2, AlexK a écrit :
> Yeah, I agree.
> It is kind of frustrating, as I know it is on the right place but ES
> gives me still YELLOW !
> I wish It was only a matter of modifying a single file in the index
> directory.
>
> Can someone share its experience on the matter ?
>
> Thanks,
> Alex.
--
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/99c81714-1815-408c-afc5-094eec5c710a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/99c81714-1815-408c-afc5-094eec5c710a%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:05am UTC](https://discuss.elastic.co/t/shard-unassigned-solutions-to-reassigned-the-shard/19163/5 "2017-07-06T01:05:43Z")