# Node can't join cluster after install x-pack plugin **URL:** \ **Category:** Elasticsearch\ **Created:** [December 21, 2016, 1:11pm UTC](https://discuss.elastic.co/t/node-cant-join-cluster-after-install-x-pack-plugin/69672 "2016-12-21T13:11:38Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Chen\_Jian](https://avatars.discourse-cdn.com/v4/letter/c/c89c15/32.png) [@Chen\_Jian](https://discuss.elastic.co/u/Chen_Jian)\ **Post date:** [December 21, 2016, 1:11pm UTC](https://discuss.elastic.co/t/node-cant-join-cluster-after-install-x-pack-plugin/69672/1 "2016-12-21T13:11:38Z")
One of my ES node unable to join cluster after install x-pack: ``` [2016-12-21T12:59:08,456][WARN][o.e.d.z.UnicastZenPing] [es2-client3.xxx.xxx] failed to send ping to [{#cloud-i-50aa2d46-0}{FYjZLUvCR4K999QndweltA}{10.1.xx.xx}{10.1.xx.xx:9300}] org.elasticsearch.transport.RemoteTransportException: [es2-client3.xxx.xxx][10.1.xx.xx:9300][internal:discovery/zen/unicast] Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No handler for action [internal:discovery/zen/unicast] at org.elasticsearch.transport.TcpTransport.handleRequest(TcpTransport.java:1329) [elasticsearch-5.1.1.jar:5.1.1] at org.elasticsearch.transport.TcpTransport.messageReceived(TcpTransport.java:1242) [elasticsearch-5.1.1.jar:5.1.1] at org.elasticsearch.transport.netty4.Netty4MessageChannelHandler.channelRead(Netty4MessageChannelHandler.java:74) [transport-netty4-5.1.1.jar:5.1.1] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293) [netty-codec-4.1.6.Final.jar:4.1.6.Final] at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:280) [netty-codec-4.1.6.Final.jar:4.1.6.Final] at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:396) [netty-codec-4.1.6.Final.jar:4.1.6.Final] at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:248) [netty-codec-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) ~[netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) ~[netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) ~[netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) ~[netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:129) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:651) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysPlain(NioEventLoop.java:536) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:490) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:450) [netty-transport-4.1.6.Final.jar:4.1.6.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) [netty-common-4.1.6.Final.jar:4.1.6.Final] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111] ``` After remove x-pack plugin, the node can join cluster again, BTW, discovery use discovery-ec2. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [December 21, 2016, 1:12pm UTC](https://discuss.elastic.co/t/node-cant-join-cluster-after-install-x-pack-plugin/69672/2 "2016-12-21T13:12:37Z")
Have you deployed X-Pack on all nodes in the cluster? ---
**Author:** ![Chen\_Jian](https://avatars.discourse-cdn.com/v4/letter/c/c89c15/32.png) [@Chen\_Jian](https://discuss.elastic.co/u/Chen_Jian)\ **Post date:** [December 21, 2016, 2:05pm UTC](https://discuss.elastic.co/t/node-cant-join-cluster-after-install-x-pack-plugin/69672/4 "2016-12-21T14:05:46Z")
not yet, is required? BTW, How can I rolling upgrade my ES cluster for x-pack deployment? ---
**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:** [December 21, 2016, 11:08pm UTC](https://discuss.elastic.co/t/node-cant-join-cluster-after-install-x-pack-plugin/69672/5 "2016-12-21T23:08:34Z")
Yes, it is required. See [http://www.elastic.co/guide/en/elasticsearch/reference/5.1/rolling-upgrades.html](http://www.elastic.co/guide/en/elasticsearch/reference/5.1/rolling-upgrades.html) ---
**Author:** ![Chen\_Jian](https://avatars.discourse-cdn.com/v4/letter/c/c89c15/32.png) [@Chen\_Jian](https://discuss.elastic.co/u/Chen_Jian)\ **Post date:** [December 22, 2016, 2:41am UTC](https://discuss.elastic.co/t/node-cant-join-cluster-after-install-x-pack-plugin/69672/6 "2016-12-22T02:41:38Z")
AFAIK, deploy x-pack will cause the node disconnect from cluster, so it's a full cluster restart upgrade rather than rolling upgrade. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 19, 2017, 2:41am UTC](https://discuss.elastic.co/t/node-cant-join-cluster-after-install-x-pack-plugin/69672/7 "2017-01-19T02:41:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.