Hi All,
For either minor or major ES upgrade (1.7.0 to 2.0.0 or 2.2.0 to 2.3.3), do I need to reopen closed indexes (lots of them) either before or after the upgrade to have those indexes upgraded to newer version?
Thanks,
Hi All,
For either minor or major ES upgrade (1.7.0 to 2.0.0 or 2.2.0 to 2.3.3), do I need to reopen closed indexes (lots of them) either before or after the upgrade to have those indexes upgraded to newer version?
Thanks,
I recently upgraded es cluster from 1.7.4 to 2.3.2, before upgrade I closed all the indices and opened them up after the upgrade.
Ended up several shards at random being not initialized at all
/_cluster/reroute?explain gives me this answer
"unassigned_info": {
"reason": "INDEX_REOPENED",
"at": "2016-05-20T05:31:35.421Z"
}
However, when I did upgrade without close/open indices, upgraded es cluster would never finish initializing shards, stuck in recovery process, emitting OOM in a few nodes repeatedly.
Well..this upgrade process is not easy for a medium-sized cluster.
© 2020. All Rights Reserved - Elasticsearch
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.