Thanks, Joerg. bin/elasticsearch -Des.node.data=true -Des.de.master=false -Des.node.name=DataOne
and curl -XPUT 'localhost:9200/testindex2/_settings' -d ' {"index" : {"number_of_replicas" : 0}}' with several restarts, have got me to a state where I see the following command-response sequence: curl "http://localhost:9200/_cluster/health?pretty=true"{ "cluster_name" : "elasticsearch", "status" : "red", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 1, "active_shards" : 1, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 33 } curl -XPOST "http://localhost:9200/testindex2/_open" {"acknowledged":false} curl -XPOST "http://localhost:9200/testindex2/_open" {"acknowledged":true} curl "http://localhost:9200/_cluster/health?pretty=true"{ "cluster_name" : "elasticsearch", "status" : "red", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 1, "active_shards" : 1, "relocating_shards" : 0, "initializing_shards" : 5, "unassigned_shards" : 33 } At one point I saw curl "http://localhost:9200/_cluster/health?pretty=true" { "cluster_name" : "elasticsearch", "status" : "yellow", "timed_out" : false, "number_of_nodes" : 2, "number_of_data_nodes" : 2, "active_primary_shards" : 17, "active_shards" : 17, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 17 } Marvel overview now shows a single node at 192.168.0.9:9300. That's 9300, not 9200. I have no idea how the second node disappeared. It looks like when I try to open testindex2, after deleting it and partially re-establishing it, Elasticsearch gets stuck while trying to initialize 5 residual shards. I'm utterly confused. I'm also motivated to learn more about node management. I'd really like to do this with a working installation. How can I untangle myself? Thanks. 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/15cd7713-a78c-4727-9de3-664837034b07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.