There's an upgrade process in the docs on the site - http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html
Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [email protected] web: www.campaignmonitor.com On 5 June 2014 00:45, Aldian <[email protected]> wrote: > Thanks you very much for the detailed reply. I will proceed this way. > Aldian > > > 2014-06-04 16:15 GMT+02:00 Nikolas Everett <[email protected]>: > >> >> >> >> 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 a topic in the >> Google Groups "elasticsearch" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elasticsearch/wF-WCPLUdQo/unsubscribe. >> To unsubscribe from this group and all its topics, 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 >> <https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3NB5x4nydx6N3ggAhqeWh%2B4LTrj_7L2ZkqYh4FCu%2BY0w%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Cordialement, > > Aldian > > -- > 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/CAECUaLxBANfsPMUq6U%2B5GPVEttMNVNUzAjYtuuGJv-0aAPMZWQ%40mail.gmail.com > <https://groups.google.com/d/msgid/elasticsearch/CAECUaLxBANfsPMUq6U%2B5GPVEttMNVNUzAjYtuuGJv-0aAPMZWQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAEM624Y9Yjwyx6x2Yt3%3DeUiL5LkEFrdbFNdpwEhVZEUHGQpD1Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
