On Wed, Jun 4, 2014 at 10:03 AM, Aldian <[email protected]> wrote: > Hi > > I am currently using elasticsearch 1.0.2. Since I have a memory leak > problem that forces me to restart it every 5 or 6 days, I am considering > upgrading to 1.2.1. But I did not found any upgrade guide, nor indications > whether new versions were retro-compatible. Please indicate if there is any > risk for the data? >
The data is compatible. Sometimes, like when Elasticsearch jumps a major version, the protocol that Elasticsearch servers use to communicate with eachother isn't backwards compatible. This is rare, and the 1.0.2->1.2.1 upgrade is fully backwards compatible. That being said, there are some issues with running a cluster with two versions of Elasticsearch: you (mostly) can't move data from a newer node to an older node. Features of the new version may degrade because they aren't getting what they need from their peers who are on the old version. This is generally OK because you won't be relying on features of the newer version until after the upgrade. The upshot: a rolling upgrade is safe for you. Turn off shard assignment on the cluster, update on node, restart elasticsearch on that node, turn shard assignment back on, wait for the cluster to go green, repeat. Make sure to upgrade any plugins that you have installed when you upgrade Elasticsearch. Nik -- 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/CAPmjWd3NB5x4nydx6N3ggAhqeWh%2B4LTrj_7L2ZkqYh4FCu%2BY0w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
