Does it affect any queries running during this process? The process does not explicitly let clusters know a node will be killed, but only stop sync and rebalancing. Are existing queries rejected or retried?
There is another option
"transient": {
"cluster.routing.allocation.exclude._ip":
}
which can 'disable' a node to restart and rebalance data. Is this one better than the approach the link says?
@warkolm The other option is by using transient.cluster.routing.allocation.exclude._ip to force the cluster to relocate all shards on a node to restart to other machines, and then restarting the node. Will this introduce less-errors?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.