# Upgrading from 0.20.6 to 1.1.1 **URL:** \ **Category:** Elasticsearch\ **Created:** [May 28, 2014, 9:33pm UTC](https://discuss.elastic.co/t/upgrading-from-0-20-6-to-1-1-1/17791 "2014-05-28T21:33:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Keith\_Webster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keith_webster/32/1532_2.png) [@Keith\_Webster](https://discuss.elastic.co/u/Keith_Webster)\ **Post date:** [May 28, 2014, 9:33pm UTC](https://discuss.elastic.co/t/upgrading-from-0-20-6-to-1-1-1/17791/1 "2014-05-28T21:33:58Z")
I currently have elasticsearch on 3 production servers with an average of 30 sites per server. Initially version 0.20.6 of elasticsearch was installed but I'd like to move them all up to 1.1.1 to take advantage of new features but also to not fall behind even more then has already happened. The option of upgrading to 1.1.1 on the servers and then regenerating all indexes is something that could be done as a last option but since each site depends on the search so extensively and would need to be down for some time I'd rather avoid that if at all possible. Here are my questions: - Do indexes created in 0.20.6 work in 1.1.1? - Has anyone ever ran more then one instance of elasticsearch, both with different version numbers on the same server? - Are there other options here that I haven't considered that someone else has used successfully in this kind of situation? Any suggestions or help is greatly appreciated. -- 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/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [May 28, 2014, 9:52pm UTC](https://discuss.elastic.co/t/upgrading-from-0-20-6-to-1-1-1/17791/2 "2014-05-28T21:52:28Z")
0.20.6 uses Lucene 3 and 1.1.1 uses Lucene 4. Lucene is always backwards compatible for at least 1 major version, so your data should be fine and there is no need to reindex. Others might disagree, but I would simply backup the data and run the latest version. An optimize might help force older segments into the latest Lucene 4 format. Prior to version 1.x, you cannot run clusters with different major versions. You will need to do a full cluster restart. If you are using a Java client, they would also need to be upgraded. > **[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. You will greatly benefit from an upgrade. The memory improvements in Lucene 4 alone (ES versions 0.90+) are worth it. Cheers, Ivan On Wed, May 28, 2014 at 2:33 PM, ciatog [keith.webster@gmail.com](mailto:keith.webster@gmail.com) wrote: > I currently have elasticsearch on 3 production servers with an average of > 30 sites per server. > > Initially version 0.20.6 of elasticsearch was installed but I'd like to > move them all up to 1.1.1 to take advantage of new features but also to not > fall behind even more then has already happened. > > The option of upgrading to 1.1.1 on the servers and then regenerating all > indexes is something that could be done as a last option but since each > site depends on the search so extensively and would need to be down for > some time I'd rather avoid that if at all possible. > > Here are my questions: > > - Do indexes created in 0.20.6 work in 1.1.1? > - Has anyone ever ran more then one instance of elasticsearch, both with > different version numbers on the same server? > - Are there other options here that I haven't considered that someone > else has used successfully in this kind of situation? > > Any suggestions or help is greatly appreciated. > > -- > 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/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.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/CALY%3DcQAUhy9sgHpBcwOoWOWe1L11Pehv9evXkzC%2BYim-xciDaw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAUhy9sgHpBcwOoWOWe1L11Pehv9evXkzC%2BYim-xciDaw%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:** [May 28, 2014, 10:19pm UTC](https://discuss.elastic.co/t/upgrading-from-0-20-6-to-1-1-1/17791/3 "2014-05-28T22:19:44Z")
Given it's prod and you don't want downtime, to be super paranoid and safe I'd upgrade to 0.90.N and then to 1.0.N and then 1.N. Force an optimise on the indexes and that will reformat them into the upgraded Lucene version (a trick someone recently mentioned), which means you don't need to reindex. I'd also leave a day between upgrades to allow for any issues to crop up. Most importantly, read the release notes and breaking changes so that any external code that interacts with your cluster can be catered for. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 29 May 2014 07:52, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > 0.20.6 uses Lucene 3 and 1.1.1 uses Lucene 4. Lucene is always backwards > compatible for at least 1 major version, so your data should be fine and > there is no need to reindex. Others might disagree, but I would simply > backup the data and run the latest version. An optimize might help force > older segments into the latest Lucene 4 format. > > Prior to version 1.x, you cannot run clusters with different major > versions. You will need to do a full cluster restart. If you are using a > Java client, they would also need to be upgraded. > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html) > > You will greatly benefit from an upgrade. The memory improvements in > Lucene 4 alone (ES versions 0.90+) are worth it. > > Cheers, > > Ivan > > On Wed, May 28, 2014 at 2:33 PM, ciatog [keith.webster@gmail.com](mailto:keith.webster@gmail.com) wrote: > > > I currently have elasticsearch on 3 production servers with an average of > > 30 sites per server. > > > > Initially version 0.20.6 of elasticsearch was installed but I'd like to > > move them all up to 1.1.1 to take advantage of new features but also to not > > fall behind even more then has already happened. > > > > The option of upgrading to 1.1.1 on the servers and then regenerating all > > indexes is something that could be done as a last option but since each > > site depends on the search so extensively and would need to be down for > > some time I'd rather avoid that if at all possible. > > > > Here are my questions: > > > > - Do indexes created in 0.20.6 work in 1.1.1? > > - Has anyone ever ran more then one instance of elasticsearch, both with > > different version numbers on the same server? > > - Are there other options here that I haven't considered that someone > > else has used successfully in this kind of situation? > > > > Any suggestions or help is greatly appreciated. > > > > -- > > 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/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3f9434b1-1958-47a2-b6db-07e32519a253%40googlegroups.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/CALY%3DcQAUhy9sgHpBcwOoWOWe1L11Pehv9evXkzC%2BYim-xciDaw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAUhy9sgHpBcwOoWOWe1L11Pehv9evXkzC%2BYim-xciDaw%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAUhy9sgHpBcwOoWOWe1L11Pehv9evXkzC%2BYim-xciDaw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAUhy9sgHpBcwOoWOWe1L11Pehv9evXkzC%2BYim-xciDaw%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/CAEM624agoNVoYdHXPQ5kiPJmhBuh9YxJ2WWchHQEdqd2dof17Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624agoNVoYdHXPQ5kiPJmhBuh9YxJ2WWchHQEdqd2dof17Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![maf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maf/32/77965_2.png) [@maf](https://discuss.elastic.co/u/maf)\ **Post date:** [June 3, 2014, 9:09am UTC](https://discuss.elastic.co/t/upgrading-from-0-20-6-to-1-1-1/17791/4 "2014-06-03T09:09:34Z")
We recently upgraded three elasticsearch clusters from 0.20.2 to 1.1.1 in one big step. We did it without any downtime by setting up parallel clusters running 1.1.1. Since our data is changing all the time we created the parallel clusters by first adding machines and shards to the existing clusters and then we manually cut off the extra machines, renamed the cluster and started them and we have a complete copy of our existing system. We only had to pause updates to the clusters for a couple of hours while rewiring some logic, and reading never stopped. -- 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/1d52a48d-d6b0-43c7-ac1b-62fe629c390f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1d52a48d-d6b0-43c7-ac1b-62fe629c390f%40googlegroups.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:25am UTC](https://discuss.elastic.co/t/upgrading-from-0-20-6-to-1-1-1/17791/5 "2017-07-06T01:25:03Z")