Partial upgrade possible?

arta · January 8, 2013, 7:23pm

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).

otisg · January 8, 2013, 10:22pm

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

Otis

ELASTICSEARCH Performance Monitoring - Sematext Monitoring | Infrastructure Monitoring Service

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
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

--

arta · January 8, 2013, 11:04pm

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?

Ivan · January 9, 2013, 12:04am

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 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?

--

arta · January 9, 2013, 1:18am

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

Dan_Fairs · January 9, 2013, 8:59am

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 | @danfairs | secondsync.com

On 9 Jan 2013, at 01:18, arta 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
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

--

--

Clinton_Gormley · January 9, 2013, 10:39am

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:

gist.github.com

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

gistfile1.md

Yesterday I upgraded our running elasticsearch cluster on a site which serves a few million search requests a day, with zero downtime. I've been asked to describe the process, hence this blogpost.

To make it more complicated, the cluster was running elasticsearch version 0.17.8 (released 6 Oct 2011) and I upgraded it to the latest 0.19.10. There have been 21 releases between those two versions, with a lot of functional changes, so I needed to be ready to roll back if necessary.

Our setup:
----------

 * *elasticsearch* 
   
   We run elasticsearch on two biggish boxes: 16 cores plus 32GB of RAM. All indices have 1 replica, so all data is stored on both boxes (about 45GB of data). The primary data for our main indices is also stored in our database.  We have a few other indices whose data is stored only in elasticsearch, but are updated once daily only. Finally, we store our sessions in elasticsearch, but active sessions are cached in memcached.

This file has been truncated. show original

hth

clint

--

Dan_Fairs · January 9, 2013, 7:28pm

Thanks Clint!

--
Dan Fairs | dan@secondsync.com | @danfairs | secondsync.com

On 9 Jan 2013, at 10:39, Clinton Gormley 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

hth

clint

--

--