# Error after upgrading to 1.0.0beta1

**URL:** <https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400>\
**Category:** Elasticsearch\
**Created:** [November 14, 2013, 8:31am UTC](https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400 "2013-11-14T08:31:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\
**Post date:** [November 14, 2013, 8:31am UTC](https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400/1 "2013-11-14T08:31:11Z")

</div>

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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [November 14, 2013, 11:30am UTC](https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400/2 "2013-11-14T11:30:15Z")

</div>

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](mailto: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](mailto:elasticsearch+unsubscribe@googlegroups.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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\
**Post date:** [November 14, 2013, 5:49pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400/3 "2013-11-14T17:49:55Z")

</div>

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](mailto: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](mailto: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](mailto:elasticsearch+unsubscribe@googlegroups.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).  
> 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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [November 14, 2013, 6:31pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400/4 "2013-11-14T18:31:57Z")

</div>

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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\
**Post date:** [November 14, 2013, 10:30pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400/5 "2013-11-14T22:30:56Z")

</div>

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](mailto:joergprante@gmail.com) \<  
[joergprante@gmail.com](mailto: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](mailto:elasticsearch+unsubscribe@googlegroups.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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [November 15, 2013, 8:14am UTC](https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400/6 "2013-11-15T08:14:08Z")

</div>

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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\
**Post date:** [November 15, 2013, 4:39pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400/7 "2013-11-15T16:39:47Z")

</div>

makes sense, Thanks Jörg.

-Amit.

On Fri, Nov 15, 2013 at 12:14 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<  
[joergprante@gmail.com](mailto: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](mailto:elasticsearch+unsubscribe@googlegroups.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).  
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, 2:06am UTC](https://discuss.elastic.co/t/error-after-upgrading-to-1-0-0beta1/14400/8 "2017-07-06T02:06:43Z")

</div>


