Elasticsearch always leaves unassigned shards on startup


(f13ts) #1

Hi,

Just getting started with ES. I'm integrating it into my Play! 2
application using the scalastic scala wrapper for the java API.

I can happily index & retrieve documents, but ONLY if I delete and recreate
my index every time the application starts, which is pretty useless.

I have a Gist showing how I start and stop a node when my application boots
up/shuts down:

and here is what my Elasticsearch-head page looks like after starting up
the app without recreating the index:

http://imgur.com/eA6AF4u

Which shows yellow status, however curl -XGET
'http://localhost:9200/_cluster/health returns RED status, and that's also
what my application reports!

Many thanks for any help/advice,

A

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2ccab4a0-6529-40eb-9f12-fc7abf10b313%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #2