Maybe I have to do this?
http://stackoverflow.com/questions/19967472/elasticsearch-unassigned-shards-how-to-fix
ie:
curl -XPUT 'localhost:9200/<index>/_settings' -d '
{"index.routing.allocation.disable_allocation": false}'
I have no idea what that does, but it can't get any more broke than it is,
so I'll give it a try...
On Thursday, April 3, 2014 10:57:39 PM UTC-4, Alexander Gray II wrote:
>
> No love. I deleted the index via the head plugin, but the index is still
> there, and the shards are still unassigned.
> Nothing in the logs showed any errors either.
> Maybe this is not the proper way to delete an index? (or maybe it got
> deleted and re-created so fast that I missed it...)
>
>
--
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 protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/54be9890-4f9d-48cb-aa39-5b28f0331ebd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
