# Upgrading from very old version of ES with zero down time

**URL:** https://discuss.elastic.co/t/upgrading-from-very-old-version-of-es-with-zero-down-time/20034
**Category:** Elasticsearch
**Created:** [October 2, 2014, 12:28am UTC](https://discuss.elastic.co/t/upgrading-from-very-old-version-of-es-with-zero-down-time/20034 "2014-10-02T00:28:02Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Eugene\_Strokin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eugene_strokin/32/1238_2.png) [@Eugene\_Strokin](https://discuss.elastic.co/u/Eugene_Strokin)
#### Post date: [October 2, 2014, 12:28am UTC](https://discuss.elastic.co/t/upgrading-from-very-old-version-of-es-with-zero-down-time/20034/1 "2014-10-02T00:28:02Z")

</div>

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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Adrian\_Luna](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@Adrian\_Luna](https://discuss.elastic.co/u/Adrian_Luna)
#### Post date: [October 2, 2014, 10:26am UTC](https://discuss.elastic.co/t/upgrading-from-very-old-version-of-es-with-zero-down-time/20034/2 "2014-10-02T10:26:16Z")

</div>

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:

> **[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.

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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/bf27a962-87cd-42aa-b47b-1ce9520307a7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/bf27a962-87cd-42aa-b47b-1ce9520307a7%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [October 2, 2014, 10:42am UTC](https://discuss.elastic.co/t/upgrading-from-very-old-version-of-es-with-zero-down-time/20034/3 "2014-10-02T10:42:07Z")

</div>

If you wish, I can prepare a knapsack backport for 0.20, then you can dump  
all your data into an archive file, and reimport the archive into a higher  
version.

Jörg

On Thu, Oct 2, 2014 at 2:28 AM, Eugene Strokin [eugene@strokin.info](mailto:eugene@strokin.info) wrote:

> 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%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/CAKdsXoHkKLYL9jGEvgJ0iMk8KBUoZ%3DL0BCpuMMfJu7MkeHBpyA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHkKLYL9jGEvgJ0iMk8KBUoZ%3DL0BCpuMMfJu7MkeHBpyA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [October 2, 2014, 2:57pm UTC](https://discuss.elastic.co/t/upgrading-from-very-old-version-of-es-with-zero-down-time/20034/4 "2014-10-02T14:57:28Z")

</div>

FYI I have prepared Knapsack plugin for Elasticsearch 0.20.6

> **[GitHub - jprante/elasticsearch-knapsack: Knapsack plugin is an import/export...](https://github.com/jprante/elasticsearch-knapsack)**
>
> Knapsack plugin is an import/export tool for Elasticsearch - GitHub - jprante/elasticsearch-knapsack: Knapsack plugin is an import/export tool for Elasticsearch

Source code tag:

> **[Release 0.20.6.2 · jprante/elasticsearch-knapsack](https://github.com/jprante/elasticsearch-knapsack/releases/tag/0.20.6.2)**
>
> 0.20.6.2

Link of Plugin ZIP for 0.20.6.2:

[http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/0.20.6.2/elasticsearch-knapsack-0.20.6.2-plugin.zip](http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/0.20.6.2/elasticsearch-knapsack-0.20.6.2-plugin.zip)

Jörg

On Thu, Oct 2, 2014 at 12:42 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<  
[joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote:

> If you wish, I can prepare a knapsack backport for 0.20, then you can dump  
> all your data into an archive file, and reimport the archive into a higher  
> version.
> 
> Jörg
> 
> On Thu, Oct 2, 2014 at 2:28 AM, Eugene Strokin [eugene@strokin.info](mailto:eugene@strokin.info)  
> wrote:
> 
> > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%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/CAKdsXoE3-htFL9XGMnOpV2WMZq9fWhj%2B9QjzJOjZty64Hdh0Ww%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE3-htFL9XGMnOpV2WMZq9fWhj%2B9QjzJOjZty64Hdh0Ww%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)
#### Post date: [October 2, 2014, 11:38pm UTC](https://discuss.elastic.co/t/upgrading-from-very-old-version-of-es-with-zero-down-time/20034/5 "2014-10-02T23:38:15Z")

</div>

Your indices should be fine as is. Lucene is guaranteed to be able to read  
data from 1 major revision prior. Elasticsearch 0.20 is Lucene 3 and the  
latest Elasticsearch is Lucene 4. Because of various bugs at the Lucene  
level, you should run an optimize (normally discouraged) to upgrade the  
indices within Lucene.

Can you hold off indexing new content during the transition? If you want  
zero downtime, it is essential. Also, what type of client are you using?  
Although the Java transport client is the most flexible, it can be an issue  
for zero downtime upgrades (with versions prior to 1.0).

If you can wait a little longer, I would hold off for Elasticsearch 1.4,  
which is currently in beta. I think it would be the biggest release since  
1.0.

Cheers,

Ivan

On Thu, Oct 2, 2014 at 7:57 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<[joergprante@gmail.com](mailto:joergprante@gmail.com)

> wrote:

> FYI I have prepared Knapsack plugin for Elasticsearch 0.20.6
> 
> [https://github.com/jprante/elasticsearch-knapsack](https://github.com/jprante/elasticsearch-knapsack)
> 
> Source code tag:
> 
> [https://github.com/jprante/elasticsearch-knapsack/releases/tag/0.20.6.2](https://github.com/jprante/elasticsearch-knapsack/releases/tag/0.20.6.2)
> 
> Link of Plugin ZIP for 0.20.6.2:
> 
> [http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/0.20.6.2/elasticsearch-knapsack-0.20.6.2-plugin.zip](http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/0.20.6.2/elasticsearch-knapsack-0.20.6.2-plugin.zip)
> 
> Jörg
> 
> On Thu, Oct 2, 2014 at 12:42 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<  
> [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote:
> 
> > If you wish, I can prepare a knapsack backport for 0.20, then you can  
> > dump all your data into an archive file, and reimport the archive into a  
> > higher version.
> > 
> > Jörg
> > 
> > On Thu, Oct 2, 2014 at 2:28 AM, Eugene Strokin [eugene@strokin.info](mailto:eugene@strokin.info)  
> > wrote:
> > 
> > > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > To view this discussion on the web visit  
> > > [https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/187ebef9-d1ce-436f-8986-c355c853b622%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/CAKdsXoE3-htFL9XGMnOpV2WMZq9fWhj%2B9QjzJOjZty64Hdh0Ww%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE3-htFL9XGMnOpV2WMZq9fWhj%2B9QjzJOjZty64Hdh0Ww%40mail.gmail.com)  
> [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE3-htFL9XGMnOpV2WMZq9fWhj%2B9QjzJOjZty64Hdh0Ww%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE3-htFL9XGMnOpV2WMZq9fWhj%2B9QjzJOjZty64Hdh0Ww%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/CALY%3DcQAOXXGjQ%3D%3DKLrsjxY41o-G9NEDBNPfzVw7T9GR\_srm5aQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAOXXGjQ%3D%3DKLrsjxY41o-G9NEDBNPfzVw7T9GR_srm5aQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### 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, 12:58am UTC](https://discuss.elastic.co/t/upgrading-from-very-old-version-of-es-with-zero-down-time/20034/6 "2017-07-06T00:58:31Z")

</div>


