There isn't a simple way to restart a node without causing it to start
But, using the new cluster level update settings API, we can allow for that.
Basically, we can have a setting that suspends allocations, you can set it
using the cluster level update settings API, and then, once the restart is
done, enable it... .
I opened an issue:
https://github.com/elasticsearch/elasticsearch/issues/1358. There is already
an issue open to allow for less distributive node restart action.
On Thu, Sep 22, 2011 at 7:30 PM, phobos182 email@example.com wrote:
ElasticSearch is re-copying all of the shards it's a replica of on restart.
Meaning that if I have a 10 node cluster, and I restart one node, the node
will copy over all of the data since the last restart. Even though the
restart lasted about 10 seconds.
Does ElasticSearch have any way to detect missing files, and just copy them
over instead of the entire index? How would I restart a node without
re-copying terabytes worth of information?
View this message in context:
Sent from the ElasticSearch Users mailing list archive at Nabble.com.