# Partial upgrade possible?

**URL:** <https://discuss.elastic.co/t/partial-upgrade-possible/10267>\
**Category:** Elasticsearch\
**Created:** [January 8, 2013, 7:23pm UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267 "2013-01-08T19:23:33Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![arta](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@arta](https://discuss.elastic.co/u/arta)\
**Post date:** [January 8, 2013, 7:23pm UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267/1 "2013-01-08T19:23:33Z")

</div>

Hi,  
I'm using 0.19.3 and it seems quite ancient version now 🙂  
So, I'm thinking of upgrade to the latest version 0.20.2.  
Also, thinking of upgrade java6 to java7.  
I have 19 data nodes and a bunch of non-data client nodes.

Can I upgrade partially?  
For example, all clients and some of data nodes stay as is (0.19.3 on Java6), while some data nodes go to newer version (ex. 0.20.2 on Java7).

---

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [January 8, 2013, 10:22pm UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267/2 "2013-01-08T22:22:35Z")

</div>

Hello,

No, this seems to cause problems - a fair number of people tried this -  
just check the ES mailing list archives:

[http://search-lucene.com/?q=cluster+upgrade+version&fc\_project=ElasticSearch&fc\_type=mail+\_hash\_+user](http://search-lucene.com/?q=cluster+upgrade+version&fc_project=ElasticSearch&fc_type=mail+_hash_+user)

## Otis

ELASTICSEARCH Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html)

On Tuesday, January 8, 2013 2:23:33 PM UTC-5, arta wrote:

> Hi,  
> I'm using 0.19.3 and it seems quite ancient version now 🙂  
> So, I'm thinking of upgrade to the latest version 0.20.2.  
> Also, thinking of upgrade java6 to java7.  
> I have 19 data nodes and a bunch of non-data client nodes.
> 
> Can I upgrade partially?  
> For example, all clients and some of data nodes stay as is (0.19.3 on  
> Java6), while some data nodes go to newer version (ex. 0.20.2 on Java7).
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/Partial-upgrade-possible-tp4027851.html](http://elasticsearch-users.115913.n3.nabble.com/Partial-upgrade-possible-tp4027851.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

--

---

<div class="post-metadata">

**Author:** ![arta](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@arta](https://discuss.elastic.co/u/arta)\
**Post date:** [January 8, 2013, 11:04pm UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267/3 "2013-01-08T23:04:24Z")

</div>

Thank you Otis, for the pointer.  
I see mixing Java6 and Java7 is not a good idea, even for clients.  
But how about ES 0.19.3 and 0.20.2?  
I could not find any related post.  
Can we mix them?

---

<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:** [January 9, 2013, 12:04am UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267/4 "2013-01-09T00:04:36Z")

</div>

You can definitely NOT have different Elasticsearch major versions between  
nodes in the same cluster (and between clients). I have also seen issues  
between minor versions (0.19.2 and 0.19.8). Each new major version of  
Elasticsearch is guaranteed to not be backwards compatible. The Lucene  
indices should be fine, but not the communication between nodes.

--  
Ivan

On Tue, Jan 8, 2013 at 3:04 PM, arta [artasano@sbcglobal.net](mailto:artasano@sbcglobal.net) wrote:

> Thank you Otis, for the pointer.  
> I see mixing Java6 and Java7 is not a good idea, even for clients.  
> But how about ES 0.19.3 and 0.20.2?  
> I could not find any related post.  
> Can we mix them?

--

---

<div class="post-metadata">

**Author:** ![arta](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@arta](https://discuss.elastic.co/u/arta)\
**Post date:** [January 9, 2013, 1:18am UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267/5 "2013-01-09T01:18:18Z")

</div>

Thank you very much Ivan.  
I will upgrade all at once, then.

---

<div class="post-metadata">

**Author:** ![Dan\_Fairs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_fairs/32/1205_2.png) [@Dan\_Fairs](https://discuss.elastic.co/u/Dan_Fairs)\
**Post date:** [January 9, 2013, 8:59am UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267/6 "2013-01-09T08:59:21Z")

</div>

Hi Arta,

I need to perform similar upgrade. It would be great to hear how it goes. If you could post your experience back to the group, that would be fantastic.

Cheers  
Dan

--  
Dan Fairs | [dan@secondsync.com](mailto:dan@secondsync.com) | @danfairs | [secondsync.com](http://secondsync.com)

On 9 Jan 2013, at 01:18, arta [artasano@sbcglobal.net](mailto:artasano@sbcglobal.net) wrote:

> Thank you very much Ivan.  
> I will upgrade all at once, then.
> 
> --  
> View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/Partial-upgrade-possible-tp4027851p4027874.html](http://elasticsearch-users.115913.n3.nabble.com/Partial-upgrade-possible-tp4027851p4027874.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
> 
> --

--

---

<div class="post-metadata">

**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\
**Post date:** [January 9, 2013, 10:39am UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267/7 "2013-01-09T10:39:21Z")

</div>

Hi all

> I need to perform similar upgrade. It would be great to hear how it  
> goes. If you could post your experience back to the group, that would  
> be fantastic.

I blogged my process for upgrading a running cluster a while back:

> <https://gist.github.com/clintongormley/3888120>

hth

clint

--

---

<div class="post-metadata">

**Author:** ![Dan\_Fairs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_fairs/32/1205_2.png) [@Dan\_Fairs](https://discuss.elastic.co/u/Dan_Fairs)\
**Post date:** [January 9, 2013, 7:28pm UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267/8 "2013-01-09T19:28:36Z")

</div>

Thanks Clint!

--  
Dan Fairs | [dan@secondsync.com](mailto:dan@secondsync.com) | @danfairs | [secondsync.com](http://secondsync.com)

On 9 Jan 2013, at 10:39, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com) wrote:

> Hi all
> 
> > I need to perform similar upgrade. It would be great to hear how it  
> > goes. If you could post your experience back to the group, that would  
> > be fantastic.
> 
> I blogged my process for upgrading a running cluster a while back:
> 
> [Upgrading a running elasticsearch cluster · GitHub](https://gist.github.com/3888120)
> 
> hth
> 
> clint
> 
> --

--

---

<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, 2:57am UTC](https://discuss.elastic.co/t/partial-upgrade-possible/10267/9 "2017-07-06T02:57:10Z")

</div>


