Hi.
I had disk space issues in a couple of the nodes of a 3-node, 5-shard,
1-replica cluster, and now all the shards are yellow, with the shard
distribution looking like this:
$ curl 127.0.0.1:9200/_cat/shards |grep my_index | sort -k4
my_index 2 r INITIALIZING 10... Dust
my_index 3 r INITIALIZING 10... Dust
my_index 0 r INITIALIZING 10... Nebulon
my_index 4 r INITIALIZING 10... Nebulon
my_index 1 r INITIALIZING 10... Letha
my_index 1 p STARTED 1198093674 187.9gb 10... Nebulon
my_index 3 p STARTED 1354081141 232.1gb 10... Letha
my_index 2 p STARTED 1833312409 315.4gb 10... Letha
my_index 4 p STARTED 337613525 47.3gb 10... Letha
my_index 0 p STARTED 714336880 119gb 10... Letha
As you can see, Letha is carrying most of the weight, with one STARTED
shard in Nebulon and none in Dust. The replicas seem to have been
corrupted. My question is: is it always safe in this situation to shut down
Dust, wipe out its data directories, and restart it? I.e., can I be
reasonably sure that there won't be any data loss? And if so, can I do it
while still indexing documents, or do I need to shut down indexing in the
meanwhile?
Thanks in advance,
Marcelo
--
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/2393cbd4-9300-4c1a-8f02-32b36539332f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.