# Elasticsearch upgrade procedure **URL:** \ **Category:** Elasticsearch\ **Created:** [June 4, 2014, 2:03pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-procedure/17907 "2014-06-04T14:03:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Aldian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aldian/32/906_2.png) [@Aldian](https://discuss.elastic.co/u/Aldian)\ **Post date:** [June 4, 2014, 2:03pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-procedure/17907/1 "2014-06-04T14:03:42Z")
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? Cheers 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6e87e53e-c041-40b0-bf34-a1bc6a3b2ee1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6e87e53e-c041-40b0-bf34-a1bc6a3b2ee1%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [June 4, 2014, 2:15pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-procedure/17907/2 "2014-06-04T14:15:17Z")
On Wed, Jun 4, 2014 at 10:03 AM, Aldian [aldian.gp@gmail.com](mailto:aldian.gp@gmail.com) 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). 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). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Aldian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aldian/32/906_2.png) [@Aldian](https://discuss.elastic.co/u/Aldian)\ **Post date:** [June 4, 2014, 2:45pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-procedure/17907/3 "2014-06-04T14:45:01Z")
Thanks you very much for the detailed reply. I will proceed this way. Aldian 2014-06-04 16:15 GMT+02:00 Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com): > On Wed, Jun 4, 2014 at 10:03 AM, Aldian [aldian.gp@gmail.com](mailto:aldian.gp@gmail.com) 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](https://groups.google.com/d/topic/elasticsearch/wF-WCPLUdQo/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > 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) > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3NB5x4nydx6N3ggAhqeWh%2B4LTrj\_7L2ZkqYh4FCu%2BY0w%40mail.gmail.com?utm\_medium=email&utm\_source=footer](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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). 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). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 4, 2014, 10:37pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-procedure/17907/4 "2014-06-04T22:37:53Z")
There's an upgrade process in the docs on the site - > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 5 June 2014 00:45, Aldian [aldian.gp@gmail.com](mailto:aldian.gp@gmail.com) 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 [nik9000@gmail.com](mailto:nik9000@gmail.com): > > > On Wed, Jun 4, 2014 at 10:03 AM, Aldian [aldian.gp@gmail.com](mailto:aldian.gp@gmail.com) 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](https://groups.google.com/d/topic/elasticsearch/wF-WCPLUdQo/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > 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) > > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3NB5x4nydx6N3ggAhqeWh%2B4LTrj\_7L2ZkqYh4FCu%2BY0w%40mail.gmail.com?utm\_medium=email&utm\_source=footer](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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > 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) > [https://groups.google.com/d/msgid/elasticsearch/CAECUaLxBANfsPMUq6U%2B5GPVEttMNVNUzAjYtuuGJv-0aAPMZWQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624Y9Yjwyx6x2Yt3%3DeUiL5LkEFrdbFNdpwEhVZEUHGQpD1Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Y9Yjwyx6x2Yt3%3DeUiL5LkEFrdbFNdpwEhVZEUHGQpD1Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:24am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-procedure/17907/5 "2017-07-06T01:24:38Z")