# Upgrading from elasticsearch 0.90.5 to 1.0.1

**URL:** https://discuss.elastic.co/t/upgrading-from-elasticsearch-0-90-5-to-1-0-1/16048
**Category:** Elasticsearch
**Created:** [February 27, 2014, 9:00am UTC](https://discuss.elastic.co/t/upgrading-from-elasticsearch-0-90-5-to-1-0-1/16048 "2014-02-27T09:00:45Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![hrishikesh\_prabhune](https://avatars.discourse-cdn.com/v4/letter/h/6f9a4e/32.png) [@hrishikesh\_prabhune](https://discuss.elastic.co/u/hrishikesh_prabhune)
#### Post date: [February 27, 2014, 9:00am UTC](https://discuss.elastic.co/t/upgrading-from-elasticsearch-0-90-5-to-1-0-1/16048/1 "2014-02-27T09:00:45Z")

</div>

Hello all,  
I have a huge elasticsearch cluster with around 150 Tb of data indexed into  
it. It has 32 nodes and more than 3000 shards in active state. I am  
planning to upgrade this elasticsearch cluster from version 0.90.5 to  
1.0.1. Are there any index compatibility issues that I need to be aware  
of? I know that 0.90.5 is based on lucene 4.4 and 1.0.1 is based on lucene  
4.6.1 (correct me if im wrong) I am not quite sure about the codecs  
compatibility between these versions of lucene indices. Can anybody shade a  
light on it?  
Are there any pointers or issues that I need to look out for in order to do  
the upgrade? Also I am not planning to do a rolling upgrade. So I am not  
worried about transport client compatibility issues.  
Thanks in advance!!

--  
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/0908af4b-b372-4d5b-8865-bdb7f78da52a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0908af4b-b372-4d5b-8865-bdb7f78da52a%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

### 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: [February 27, 2014, 9:20am UTC](https://discuss.elastic.co/t/upgrading-from-elasticsearch-0-90-5-to-1-0-1/16048/2 "2014-02-27T09:20:13Z")

</div>

You might want to do an few minor upgrades before to ensure you don't take  
a massive leap with lucene, I recall some people have had issues with that.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 27 February 2014 20:00, hrishikesh prabhune [hruship@gmail.com](mailto:hruship@gmail.com) wrote:

> Hello all,  
> I have a huge elasticsearch cluster with around 150 Tb of data indexed  
> into it. It has 32 nodes and more than 3000 shards in active state. I am  
> planning to upgrade this elasticsearch cluster from version 0.90.5 to  
> 1.0.1. Are there any index compatibility issues that I need to be aware  
> of? I know that 0.90.5 is based on lucene 4.4 and 1.0.1 is based on lucene  
> 4.6.1 (correct me if im wrong) I am not quite sure about the codecs  
> compatibility between these versions of lucene indices. Can anybody shade a  
> light on it?  
> Are there any pointers or issues that I need to look out for in order to  
> do the upgrade? Also I am not planning to do a rolling upgrade. So I am not  
> worried about transport client compatibility issues.  
> Thanks in advance!!
> 
> --  
> 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/0908af4b-b372-4d5b-8865-bdb7f78da52a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0908af4b-b372-4d5b-8865-bdb7f78da52a%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CAEM624Z\_FeykQ3Xh2T\_hJ-DFt-rboPRxNEZ3VhFO%2BEfmbM9r2w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Z_FeykQ3Xh2T_hJ-DFt-rboPRxNEZ3VhFO%2BEfmbM9r2w%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

### Author: ![Jilles\_van\_Gurp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jilles_van_gurp/32/879_2.png) [@Jilles\_van\_Gurp](https://discuss.elastic.co/u/Jilles_van_Gurp)
#### Post date: [February 28, 2014, 11:25am UTC](https://discuss.elastic.co/t/upgrading-from-elasticsearch-0-90-5-to-1-0-1/16048/3 "2014-02-28T11:25:09Z")

</div>

You should take note of the compatibility breaking changes in the release  
notes of course and do some functional tests with the new version to ensure  
that you are not affected by those changes. Additionally, I would carefully  
plan and test the update procedure with a smaller cluster first. In theory,  
you should be able to do a rolling restart with the new version but that  
still is a somewhat risky procedure where there is some room for unexpected  
outages. Doing upgrades like this without any downtime can be challenging.

The easiest is to just shutdown the whole cluster, upgrade all the nodes  
and then bring it back up. When I did this a few weeks ago with my logstash  
cluster (0.90.8 -\> 1.0.0), it spent about 15 minutes converting my indices  
before the cluster went green again. That was a small setup with only 10GB.  
The differences between 0.90.5 and 1.0.0 are not such that I would perform  
any upgrades to in between versions. The risks for those upgrades are  
similar to doing the proper upgrade to 1.0.0 directly probably. You'd have  
to deal with several lucene updates and index conversions.

Jilles

On Thursday, February 27, 2014 10:00:45 AM UTC+1, hrishikesh prabhune wrote:

> Hello all,  
> I have a huge elasticsearch cluster with around 150 Tb of data indexed  
> into it. It has 32 nodes and more than 3000 shards in active state. I am  
> planning to upgrade this elasticsearch cluster from version 0.90.5 to  
> 1.0.1. Are there any index compatibility issues that I need to be aware  
> of? I know that 0.90.5 is based on lucene 4.4 and 1.0.1 is based on lucene  
> 4.6.1 (correct me if im wrong) I am not quite sure about the codecs  
> compatibility between these versions of lucene indices. Can anybody shade a  
> light on it?  
> Are there any pointers or issues that I need to look out for in order to  
> do the upgrade? Also I am not planning to do a rolling upgrade. So I am not  
> worried about transport client compatibility issues.  
> Thanks in advance!!

--  
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/13be09f0-4d10-4664-a56a-6d449cdca057%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/13be09f0-4d10-4664-a56a-6d449cdca057%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 1:46am UTC](https://discuss.elastic.co/t/upgrading-from-elasticsearch-0-90-5-to-1-0-1/16048/4 "2017-07-06T01:46:38Z")

</div>


