# Elasticsearch upgrade from 1.7 to 2.4 **URL:** \ **Category:** Elasticsearch\ **Created:** [October 13, 2016, 8:57pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-7-to-2-4/62999 "2016-10-13T20:57:29Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Tarun\_Hasija](https://avatars.discourse-cdn.com/v4/letter/t/a698b9/32.png) [@Tarun\_Hasija](https://discuss.elastic.co/u/Tarun_Hasija)\ **Post date:** [October 13, 2016, 8:57pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-7-to-2-4/62999/1 "2016-10-13T20:57:29Z")
Hi On upgrading elasticsearch from 1.7 to 2.4 and setting the network.host to _eth4_(network interface address) , We see the below Warning messages in the cluster logs . These warning messages are continuously coming u in the logs. Please let us know if there is a fix for this or if its a new bug which needs to be created. [2016-10-13 15:56:53,479][WARN][transport.netty] [rd2-n01-elk] exception caught on transport layer [[id: 0xe0af7462, /172.29.70.135:52047 =\> /172.29.70.138:9300]], closing connection java.lang.IllegalStateException: Received message from unsupported version: [1.0.0] minimal compatible version is: [2.0.0] at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:110) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:75) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [October 13, 2016, 9:09pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-7-to-2-4/62999/2 "2016-10-13T21:09:33Z")
Looks like you are trying to connect to the cluster with a 1.x version of the transport client which isn't supported. It is also possible that you have a 1.x version of Elasticsearch trying to connect to the cluster which also isn't supported. ---
**Author:** ![Tarun\_Hasija](https://avatars.discourse-cdn.com/v4/letter/t/a698b9/32.png) [@Tarun\_Hasija](https://discuss.elastic.co/u/Tarun_Hasija)\ **Post date:** [October 13, 2016, 9:48pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-7-to-2-4/62999/3 "2016-10-13T21:48:16Z")
Hi Nik Everett No I am not connecting with 1.x version of the transport client. The logs I gave above are from the master only node in the cluster , also one data only node has these warning in the logs. We just have the reindexing plugin that was already installed before the upgrade was started, the plugin is still installed after the upgrade. Can the plugin cause these warnings ? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:12pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-7-to-2-4/62999/4 "2017-07-05T22:12:32Z")