I am using ElasticSearch 1.2.0.
I have a question about the solution to solve the "Shard unassigned"
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/elasticsearch 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
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
If it was so simple...
The new cluster showed the old kibana-int index as unassigned despite
restart of the service.
- 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
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 email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2fce0328-56f2-4a6c-9343-c4808e983549%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.