# Can not connect to two different version clusters using transport client **URL:** \ **Category:** Elasticsearch\ **Created:** [November 12, 2013, 4:51am UTC](https://discuss.elastic.co/t/can-not-connect-to-two-different-version-clusters-using-transport-client/14360 "2013-11-12T04:51:56Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![spancer\_ray](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spancer_ray/32/76303_2.png) [@spancer\_ray](https://discuss.elastic.co/u/spancer_ray)\ **Post date:** [November 12, 2013, 4:51am UTC](https://discuss.elastic.co/t/can-not-connect-to-two-different-version-clusters-using-transport-client/14360/1 "2013-11-12T04:51:56Z")
Hi Guys, I'm now using java transport client to connect two clusters in different versions. One is 0.90.0 (on remote server), the other is 1.0.0.Beta1 (set up on my local machine). And my client ES version is 0.90.0. It seems the client es version has to match the server's, so I can't connect to them at the same time (No node available). Now I'm trying to migrate data from 0.90.0 to 1.0.0Beta1 for some new features' test. Blocked here. Can anyone help? BTW, two clusters hold different cluster names. Exception message: 12:47:14,758 INFO transport:119 - [Sunfire] failed to get node info for [#transport#-1][inet[/127.0.0.1:9300]], disconnecting... org.elasticsearch.transport.RemoteTransportException: [Jeffries, Madison][inet[/127.0.0.1:9300]][] Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No handler for action [] at org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:206) at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:109) at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:296) at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Exception in thread "main" org.elasticsearch.client.transport.NoNodeAvailableException: No node available at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:205) at org.elasticsearch.client.transport.support.InternalTransportClient.execute(InternalTransportClient.java:106) at org.elasticsearch.client.support.AbstractClient.bulk(AbstractClient.java:149) at org.elasticsearch.client.transport.TransportClient.bulk(TransportClient.java:345) at org.elasticsearch.action.bulk.BulkProcessor.execute(BulkProcessor.java:286) at org.elasticsearch.action.bulk.BulkProcessor.executeIfNeeded(BulkProcessor.java:260) at org.elasticsearch.action.bulk.BulkProcessor.internalAdd(BulkProcessor.java:240) at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:234) at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:230) at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:216) Thanks, Spancer ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 12, 2013, 6:14am UTC](https://discuss.elastic.co/t/can-not-connect-to-two-different-version-clusters-using-transport-client/14360/2 "2013-11-12T06:14:57Z")
You should update your client to latest (1.0.0). It could work with some 0.90.x versions (not sure for 0.90.0 though). If you don't want to Check cluster name , set: client.transport.ignore\_cluster\_name See [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html#transport-client) -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 12 nov. 2013 à 05:51, spancer ray [spancer.roc.ray@gmail.com](mailto:spancer.roc.ray@gmail.com) a écrit : > Hi Guys, > > I'm now using java transport client to connect two clusters in different > versions. One is 0.90.0 (on remote server), the other is 1.0.0.Beta1 (set up > on my local machine). And my client ES version is 0.90.0. It seems the > client es version has to match the server's, so I can't connect to them at > the same time. Now I'm trying to migrate data from 0.90.0 to 1.0.0Beta1 for > some new features' test. Blocked here. > > Can anyone help? BTW, two clusters hold different cluster names. > > Thanks, > Spancer > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/connect-to-two-different-version-clusters-using-transport-client-tp4044126.html](http://elasticsearch-users.115913.n3.nabble.com/connect-to-two-different-version-clusters-using-transport-client-tp4044126.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > 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). ---
**Author:** ![spancer\_ray](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spancer_ray/32/76303_2.png) [@spancer\_ray](https://discuss.elastic.co/u/spancer_ray)\ **Post date:** [November 14, 2013, 3:43am UTC](https://discuss.elastic.co/t/can-not-connect-to-two-different-version-clusters-using-transport-client/14360/3 "2013-11-14T03:43:20Z")
Thanks, David, I tried on windows but failed. Goona try on linux. Spancer ---
**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:07am UTC](https://discuss.elastic.co/t/can-not-connect-to-two-different-version-clusters-using-transport-client/14360/4 "2017-07-06T02:07:19Z")