You can get it to green if you get rid of the replicas - curl -XPUT
localhost:9200/*/_settings -d '{ "index" : { "number_of_replicas" : 0 } }'On 26 November 2014 at 09:36, Pitaga <[email protected]> wrote: > Doing a thorough job of deleting all indexes got my installation back to > status yellow, apparently fully functional when I re-established my test > index with a new name. Sledgehammer, but I didn't need to sow the ground > with salt. > > On Friday, November 21, 2014 11:21:26 AM UTC-8, Pitaga wrote: >> >> When I shutdown and restart Elasticsearch on my Ubuntu laptop, the >> status is yellow until I attempt to open an index, at which time the status >> changes to red. The output for >> >> curl "http://localhost:9200/_cluster/health?pretty=true"; >> >> is >> >> { >> "cluster_name" : "elasticsearch", >> "status" : "red", >> "timed_out" : false, >> "number_of_nodes" : 1, >> "number_of_data_nodes" : 1, >> "active_primary_shards" : 2, >> "active_shards" : 2, >> "relocating_shards" : 0, >> "initializing_shards" : 5, >> "unassigned_shards" : 7 >> } >> >> I've tried deleting all but one index, shutting down and restarting. I've >> also tried issuing >> >> curl -XPUT 'localhost:9200/testindex2/_settings' -d >> '{"index.routing.allocation.disable_allocation": false}' >> >> shutting down and restarting. I've also tried issuing >> >> curl XPOST 'http://localhost:9200/_cluster/reroute?pretty=true' -d >> '{"commands" : [ { "allocate" : { "index" : "testindex1", "shard" : 4 , >> "node" : "gdVC517DR4OiE0v44_1n5A", "allow_primary" : 1 } }]}’ >> >> for one particular index and shard, with no apparent effect on the output >> of >> >> curl -XGET http://localhost:9200/_cluster/state?pretty=true >> >> In each case, I shutdown with >> >> curl -XPOST 'http://localhost:9200/_shutdown' >> >> and restarted with >> >> /etc/init.d/elasticsearch restart >> >> The one remaining undeleted index is currently used only for >> experimentation. I can delete and then re-establish it if necessary. Or I >> can apply a bigger sledgehammer if necessary. >> >> I found elements of diagnostics and suggested solutions by searching the >> web. I am not now, and possibly I will never be, a qualified Elasticsearch >> administrator. I'd be grateful for suggestions on how to fix this, in terms >> a child can understand. >> > -- > 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/44983fbf-dc7d-498a-9e34-387124fa3225%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/44983fbf-dc7d-498a-9e34-387124fa3225%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZ%3DOw80b9R%3Dt8edySUf_pZyxH4N83axkTaStoPOaEn%2BHiQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
