# Errors upgrading from es 0.17.7 to 0.18.2 **URL:** \ **Category:** Elasticsearch\ **Created:** [October 31, 2011, 1:45pm UTC](https://discuss.elastic.co/t/errors-upgrading-from-es-0-17-7-to-0-18-2/5727 "2011-10-31T13:45:38Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![surielb](https://avatars.discourse-cdn.com/v4/letter/s/eb8c5e/32.png) [@surielb](https://discuss.elastic.co/u/surielb)\ **Post date:** [October 31, 2011, 1:45pm UTC](https://discuss.elastic.co/t/errors-upgrading-from-es-0-17-7-to-0-18-2/5727/1 "2011-10-31T13:45:38Z")
Attempting to upgrade our cluster from v 0.17.7 of es to the latest 0.18.2 results in the updated nodes not being able to join the cluster and loop the following warning: [2011-10-31 16:24:09,723][WARN][transport.netty] [James Howlett] Message not fully read (request) for [132808] and action [discovery/zen/multicast], resetting attempting to load the data into a new cluster fails too. Ideas? Help? anyone? Thanks, ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 31, 2011, 5:30pm UTC](https://discuss.elastic.co/t/errors-upgrading-from-es-0-17-7-to-0-18-2/5727/2 "2011-10-31T17:30:44Z")
Is there a chance that a node with a 0.17 node version is joining a node with 0.18 version? There is no support (yet) for cross major version nodes cluster. On Mon, Oct 31, 2011 at 3:45 PM, surielb [suriel@conduit.com](mailto:suriel@conduit.com) wrote: > Attempting to upgrade our cluster from v 0.17.7 of es to the latest 0.18.2 > results in the updated nodes not being able to join the cluster and loop > the > following warning: > > [2011-10-31 16:24:09,723][WARN][transport.netty] [James Howlett] > Message not fully read (request) for [132808] and action > [discovery/zen/multicast], resetting > > attempting to load the data into a new cluster fails too. > > Ideas? Help? anyone? > > Thanks, > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Errors-upgrading-from-es-0-17-7-to-0-18-2-tp3467850p3467850.html](http://elasticsearch-users.115913.n3.nabble.com/Errors-upgrading-from-es-0-17-7-to-0-18-2-tp3467850p3467850.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![surielb](https://avatars.discourse-cdn.com/v4/letter/s/eb8c5e/32.png) [@surielb](https://discuss.elastic.co/u/surielb)\ **Post date:** [October 31, 2011, 6:35pm UTC](https://discuss.elastic.co/t/errors-upgrading-from-es-0-17-7-to-0-18-2/5727/3 "2011-10-31T18:35:38Z")
I gathered there was no support however I could not load the data into a new cluster in any way, was there a change in the file structure? Also is there any best practice for upgrading a live cluster? Suriel Bendahan On Oct 31, 2011, at 19:31, "kimchy [via Elasticsearch Users]" [ml-node+s115913n3468416h35@n3.nabble.com](mailto:ml-node+s115913n3468416h35@n3.nabble.com) wrote: > Is there a chance that a node with a 0.17 node version is joining a node with 0.18 version? There is no support (yet) for cross major version nodes cluster. > > On Mon, Oct 31, 2011 at 3:45 PM, surielb \<[hidden email]\\> wrote: > Attempting to upgrade our cluster from v 0.17.7 of es to the latest 0.18.2 > results in the updated nodes not being able to join the cluster and loop the > following warning: > > [2011-10-31 16:24:09,723][WARN][transport.netty] [James Howlett] > Message not fully read (request) for [132808] and action > [discovery/zen/multicast], resetting > > attempting to load the data into a new cluster fails too. > > Ideas? Help? anyone? > > Thanks, > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/Errors-upgrading-from-es-0-17-7-to-0-18-2-tp3467850p3467850.html](http://elasticsearch-users.115913.n3.nabble.com/Errors-upgrading-from-es-0-17-7-to-0-18-2-tp3467850p3467850.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > * * * > > If you reply to this email, your message will be added to the discussion below: > [http://elasticsearch-users.115913.n3.nabble.com/Errors-upgrading-from-es-0-17-7-to-0-18-2-tp3467850p3468416.html](http://elasticsearch-users.115913.n3.nabble.com/Errors-upgrading-from-es-0-17-7-to-0-18-2-tp3467850p3468416.html) > To unsubscribe from Errors upgrading from es 0.17.7 to 0.18.2, click here[http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe\_by\_code&node=3467850&code=c3VyaWVsQGNvbmR1aXQuY29tfDM0Njc4NTB8LTYxMjg5ODU0OQ==](http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3467850&code=c3VyaWVsQGNvbmR1aXQuY29tfDM0Njc4NTB8LTYxMjg5ODU0OQ==). ---
**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, 3:50am UTC](https://discuss.elastic.co/t/errors-upgrading-from-es-0-17-7-to-0-18-2/5727/4 "2017-07-06T03:50:20Z")