Error after upgrading to 1.0.0beta1

Elastic Stack Elasticsearch
1

Hi all - I just upgraded from version 0.90.6 to beta1 and ever since then
have been seeing the following errors: any clue what might have gone wrong?

[WARN ][transport.netty ] [Firebird] Message not fully read
(request) for [2465] and action [], resetting

-Amit.

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

Hey,

first, thanks a lot for testing the beta!

Do you have client nodes or transport clients connecting to your cluster,
which still use an older client maybe?

--Alex

On Thu, Nov 14, 2013 at 9:31 AM, Amit Soni amitsoni29@gmail.com wrote:

Hi all - I just upgraded from version 0.90.6 to beta1 and ever since then
have been seeing the following errors: any clue what might have gone wrong?

[WARN ][transport.netty ] [Firebird] Message not fully read
(request) for [2465] and action [], resetting

-Amit.

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

yes, thanks Alex. I think that is exactly the problem. I had a client which
was on 0.90.6.

While thinking through it, I am wondering when we upgrade do we need to
shut down the clients (if they are on different versions)?

Also any recommendation on a right approach to do an upgrade would be great.

-Amit.

On Thu, Nov 14, 2013 at 3:30 AM, Alexander Reelsen alr@spinscale.de wrote:

Hey,

first, thanks a lot for testing the beta!

Do you have client nodes or transport clients connecting to your cluster,
which still use an older client maybe?

--Alex

On Thu, Nov 14, 2013 at 9:31 AM, Amit Soni amitsoni29@gmail.com wrote:

Hi all - I just upgraded from version 0.90.6 to beta1 and ever since then
have been seeing the following errors: any clue what might have gone wrong?

[WARN ][transport.netty ] [Firebird] Message not fully read
(request) for [2465] and action [], resetting

-Amit.

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

4

Yes, you must take down all clients and upgrade them also to 1.0.0 beta
(unless they use HTTP which is probably ok to continue)

Jörg

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

5

Thanks Jörg. Is this required only during major version upgrade? Can minor
version upgrades be done without bringing the transport clients down?

-Amit.

On Thu, Nov 14, 2013 at 10:31 AM, joergprante@gmail.com <
joergprante@gmail.com> wrote:

Yes, you must take down all clients and upgrade them also to 1.0.0 beta
(unless they use HTTP which is probably ok to continue)

Jörg

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

6

To be honest, I would like that all client versions of 0.90 were compatible
but they are not, due to subtle ES Java API changes. It may be a bit
unfortunate that server API changes can propagate to the client, because
the ES code base for server and client is the same (the transport client
communication and cluster node communication is the using the same code).

I hope, after 1.0.0 release, the ES core team can establish a strategy of
(minor) bug fix versions and (major) feature versions with foreseeable
breaking changes.

Jörg

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

7

makes sense, Thanks Jörg.

-Amit.

On Fri, Nov 15, 2013 at 12:14 AM, joergprante@gmail.com <
joergprante@gmail.com> wrote:

To be honest, I would like that all client versions of 0.90 were
compatible but they are not, due to subtle ES Java API changes. It may be a
bit unfortunate that server API changes can propagate to the client,
because the ES code base for server and client is the same (the transport
client communication and cluster node communication is the using the same
code).

I hope, after 1.0.0 release, the ES core team can establish a strategy of
(minor) bug fix versions and (major) feature versions with foreseeable
breaking changes.

Jörg

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