I would just start another node (or a couple of nodes for security reasons, mantaining replicas in different machines, etc.) in your cluster with the new ES version, wait untill data gets copied, turn off every deprecated (old) version of ES and then restart the nodes you turned-off with after updating its version.
Alternatively, you can also do something similar to this: http://www.elasticsearch.org/blog/changing-mapping-with-zero-downtime/ Hope some of this helps. El jueves, 2 de octubre de 2014 02:28:02 UTC+2, Eugene Strokin escribió: > > Hello, > my ES cluster is still running version 0.20.1. It is time to upgrade. I > know I cannot just use indexes as is and replace the jars by the newest ES. > They are not compatible as far as I understood. > So I need to set up a parallel cluster with the newest ES and some how > transfer all the data with zero down time. The size of the indexes is about > 100Gb and the traffic is relatively big, so it could take some time, and > somehow I need to keep the clusters in sync. > Did someone had such experience? > Does someone have any suggestions how to approach this? > I cannot come up with some elegant solution. > Any help is greatly appreciated. > Thank you, > Eugene > > -- 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/bf27a962-87cd-42aa-b47b-1ce9520307a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
