Upgrade Java on existing nodes

Elastic Stack Elasticsearch
1

Hey guys, I have 3 nodes, one of which I just added recently, ever since I
keep seeing this error "Failed to deserialize exception response from
stream". The only thing I see different in the new node is the java version
which is newer in the new node. I wanted to upgrade the version on the old
nodes but was wondering if any of you has done this before or if there is
any problems that could arise

Thanks for the help

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

2

Shut down a node, install new Java, start the node, then move to the
next node. But consider there may be a downtime while nodes are
recovering after start. In my case 15-20 minutes. If you let recover
each node before moving on to the next node, there is no interruption of
service. Or just stop all nodes, update java, and restart nodes again.
It's easy and the fastest method I know but service is interrupted.

Jörg

Am 06.03.13 18:54, schrieb Manuel Gomez:

Hey guys, I have 3 nodes, one of which I just added recently, ever
since I keep seeing this error "Failed to deserialize exception
response from stream". The only thing I see different in the new node
is the java version which is newer in the new node. I wanted to
upgrade the version on the old nodes but was wondering if any of you
has done this before or if there is any problems that could arise

Thanks for the help

--
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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

3

Thanks Jörg. I thought about doing this. I just didn't know if my nodes
would recover from it. I'll give this a try and report back

On Wed, Mar 6, 2013 at 3:03 PM, Jörg Prante joergprante@gmail.com wrote:

Shut down a node, install new Java, start the node, then move to the next
node. But consider there may be a downtime while nodes are recovering after
start. In my case 15-20 minutes. If you let recover each node before moving
on to the next node, there is no interruption of service. Or just stop all
nodes, update java, and restart nodes again. It's easy and the fastest
method I know but service is interrupted.

Jörg

Am 06.03.13 18:54, schrieb Manuel Gomez:

Hey guys, I have 3 nodes, one of which I just added recently, ever since
I keep seeing this error "Failed to deserialize exception response from
stream". The only thing I see different in the new node is the java version
which is newer in the new node. I wanted to upgrade the version on the old
nodes but was wondering if any of you has done this before or if there is
any problems that could arise

Thanks for the help

--
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.comelasticsearch%2Bunsubscribe@googlegroups.com
.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/**
topic/elasticsearch/**LPA6Xb02Jvk/unsubscribe?hl=en-**UShttps://groups.google.com/d/topic/elasticsearch/LPA6Xb02Jvk/unsubscribe?hl=en-US
.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@**googlegroups.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://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.
For more options, visit https://groups.google.com/groups/opt_out.

4

Yes. As Jörg said, it's sometimes better to have one minute of full interruption than one hour of doing some recovery process without real interruption.
Also be aware that you need enough disk space to have replicas copied to the remaining nodes.

My 2 cents

David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 6 mars 2013 à 19:03, Jörg Prante joergprante@gmail.com a écrit :

Shut down a node, install new Java, start the node, then move to the next node. But consider there may be a downtime while nodes are recovering after start. In my case 15-20 minutes. If you let recover each node before moving on to the next node, there is no interruption of service. Or just stop all nodes, update java, and restart nodes again. It's easy and the fastest method I know but service is interrupted.

Jörg

Am 06.03.13 18:54, schrieb Manuel Gomez:

Hey guys, I have 3 nodes, one of which I just added recently, ever since I keep seeing this error "Failed to deserialize exception response from stream". The only thing I see different in the new node is the java version which is newer in the new node. I wanted to upgrade the version on the old nodes but was wondering if any of you has done this before or if there is any problems that could arise

Thanks for the help

--
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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.