Brian, thanks for the help on correcting what I've been doing. Once I get
my system unwedged, I won't mix curl commands and scripts.
I deleted the one remaining index that I had established, and then all the
remaining .marvel indexes. Then I re-established mapping and settings for
my index. When I tried to open the index, I got an '"acknowledged" : false'
response on the first try, and an '"acknowledged" : true' response on the
second try. When I tried to put a document in this index, I got
"error":"UnavailableShardsException[[testindex2][3] [2] shardIt, [0]
active : Timeout waiting for [1m] ...
According to what I've read, even if I uninstall and re-install
Elasticsearch on my laptop, it might be unusable. I expect a need a tweezer
fix that's informed by knowledge of how Elasticsearch manages shards. I'd
be grateful for possible recipes on how to fix this, and also for a pointer
to a clear and concise description of Elasticsearch shard management.
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/8f4a5795-eec6-4415-acef-16d8bc29e63b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
