# Elasticsearch multi-layer remote cluster is invalid **URL:** \ **Category:** Elasticsearch\ **Tags:** ccs-cross-cluster-search\ **Created:** [April 29, 2020, 3:39am UTC](https://discuss.elastic.co/t/elasticsearch-multi-layer-remote-cluster-is-invalid/230294 "2020-04-29T03:39:46Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jiankunking](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jiankunking/32/39320_2.png) [@jiankunking](https://discuss.elastic.co/u/jiankunking)\ **Post date:** [April 29, 2020, 3:39am UTC](https://discuss.elastic.co/t/elasticsearch-multi-layer-remote-cluster-is-invalid/230294/1 "2020-04-29T03:39:46Z")
Initial requirements [elastic/kibana#64267](https://github.com/elastic/kibana/issues/64267) Set up the es cluster as shown below： [![1](https://us1.discourse-cdn.com/elastic/original/3X/9/b/9bd1e2fd3cf0615389807410498af97d0d1d0119.png)](https://user-images.githubusercontent.com/15723050/80473969-75e1c580-8979-11ea-8336-98119bbe1da0.png) However, the following anomalies are found: `at org.elasticsearch.transport.InboundHandler.handleResponse(InboundHandler.java:214) ~[elasticsearch-7.6.2.jar:7.6.2]", "at org.elasticsearch.transport.InboundHandler.messageReceived(InboundHandler.java:139) ~[elasticsearch-7.6.2.jar:7.6.2]", "at org.elasticsearch.transport.InboundHandler.inboundMessage(InboundHandler.java:103) ~[elasticsearch-7.6.2.jar:7.6.2]", "at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:300) ~[?:?]", "at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374) ~[?:?]", "at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374) ~[?:?]", "at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360) ~[?:?]", "at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[?:?]", "stacktrace": ["org.elasticsearch.transport.ConnectTransportException: [][10.133.0.89:9300] general node connection failure", "at org.elasticsearch.action.ActionListener$1.onFailure(ActionListener.java:71) ~[elasticsearch-7.6.2.jar:7.6.2]", "at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.6.2.jar:7.6.2]", "at org.elasticsearch.transport.InboundHandler.inboundMessage(InboundHandler.java:103) ~[elasticsearch-7.6.2.jar:7.6.2]", "at org.elasticsearch.transport.netty4.Netty4MessageChannelHandler.channelRead(Netty4MessageChannelHandler.java:62) ~[?:?]", "at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352) ~[?:?]", "at io.netty.handler.logging.LoggingHandler.channelRead(LoggingHandler.java:241) ~[?:?]", "Caused by: java.lang.IllegalStateException: Received message from unsupported version: [6.5.1] minimal compatible version is: [6.8.0]", "stacktrace": ["org.elasticsearch.transport.ConnectTransportException: [][10.163.204.195:9300] general node connection failure", "at org.elasticsearch.transport.TcpTransport$ChannelsConnectedListener.lambda$onResponse$2(TcpTransport.java:979) ~[elasticsearch-7.6.2.jar:7.6.2]", "at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.6.2.jar:7.6.2]", "at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374) ~[?:?]", "at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163) ~[?:?]", "at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1422) ~[?:?]", "at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374) ~[?:?]", "at io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1050) ~[?:?]", "at org.elasticsearch.transport.TransportHandshaker$HandshakeResponseHandler.handleResponse(TransportHandshaker.java:139) ~[elasticsearch-7.6.2.jar:7.6.2]", "at org.elasticsearch.common.util.concurrent.EsExecutors$DirectExecutorService.execute(EsExecutors.java:225) ~[elasticsearch-7.6.2.jar:7.6.2]", "at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1422) ~[?:?]", "at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360) ~[?:?]", "at io.netty.handler.logging.LoggingHandler.channelRead(LoggingHandler.java:241) ~[?:?]", "at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:554) ~[?:?]", "at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:514) ~[?:?]` So I rebuilt the es cluster, as shown in the following figure: [![2](https://us1.discourse-cdn.com/elastic/original/3X/7/2/7207128611def496a0c009c49b4cf549367ad0bd.png)](https://user-images.githubusercontent.com/15723050/80475306-46cc5380-897b-11ea-9a64-01de13caee6e.png) However, I found that in kibana, I still could not see the data of each es cluster in the blue box。 **Is it because remote cluster cannot multilayer proxy?** ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 29, 2020, 4:04am UTC](https://discuss.elastic.co/t/elasticsearch-multi-layer-remote-cluster-is-invalid/230294/2 "2020-04-29T04:04:25Z")
Is this in relation to cross cluster search? ---
**Author:** ![jiankunking](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jiankunking/32/39320_2.png) [@jiankunking](https://discuss.elastic.co/u/jiankunking)\ **Post date:** [April 30, 2020, 7:57am UTC](https://discuss.elastic.co/t/elasticsearch-multi-layer-remote-cluster-is-invalid/230294/3 "2020-04-30T07:57:22Z")
Yes, I feel there is a problem after many times of remote cluster ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 28, 2020, 7:57am UTC](https://discuss.elastic.co/t/elasticsearch-multi-layer-remote-cluster-is-invalid/230294/4 "2020-05-28T07:57:25Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.