是时候用 ES 拯救发际线啦

本来集群好好的,突然连接master失败,有大神能给指点一下方向吗?

Elasticsearch | 作者 Leeeo | 发布于2019年01月09日 | 阅读数:8410

软件版本:es6.2.2
 [2019-01-09T09:42:56,518][WARN ][c.f.s.s.t.SearchGuardSSLNettyTransport] [node-143] send message failed [channel: NettyTcpChannel{localAddress=/192.168.30.143:9300, remoteAddress=/192.168.30.142:28933}]
java.nio.channels.ClosedChannelException: null
        at io.netty.channel.AbstractChannel$AbstractUnsafe.write(...)(Unknown Source) ~[?:?]

[2019-01-09T09:43:01,914][INFO ][o.e.d.z.ZenDiscovery     ] [node-143] master_left [{node-141}{3kWs-rFaR_yZVZOpRp1BFA}{IX0VLJigSja-z6yCR5TIjg}{192.168.30.141}{192.168.30.141:9300}], reason [failed to ping, tried [3] times, each with  maximum [30s] timeout]
[2019-01-09T09:43:01,914][WARN ][o.e.d.z.ZenDiscovery     ] [node-143] master left (reason = failed to ping, tried [3] times, each with  maximum [30s] timeout), current nodes: nodes:
   {node-141}{3kWs-rFaR_yZVZOpRp1BFA}{IX0VLJigSja-z6yCR5TIjg}{192.168.30.141}{192.168.30.141:9300}, master
   {node-142}{aYMFcfn3RvKDVfgncxC8cQ}{omgwMmmaTpWlmVs2Xk7eqw}{192.168.30.142}{192.168.30.142:9300}
   {node-143}{gIvN8KNiQsmY2Lsy20Expg}{7KJGWwp7Rg6GpEJqCkziXA}{192.168.30.143}{192.168.30.143:9300}, local

[2019-01-09T09:43:15,005][INFO ][o.e.d.z.ZenDiscovery     ] [node-143] failed to send join request to master [{node-141}{3kWs-rFaR_yZVZOpRp1BFA}{IX0VLJigSja-z6yCR5TIjg}{192.168.30.141}{192.168.30.141:9300}], reason [RemoteTransportException[[node-141][192.168.30.141:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[node-143][192.168.30.143:9300] general node connection failure]; nested: IllegalStateException[handshake failed]; nested: TransportException[connection reset]; ]
已邀请:

bean

赞同来自: chenzetan zhou_elk

遇到同样的问题,楼主找出来问题原因了嘛

zqc0512 - andy zhou

赞同来自:

reason [failed to ping, tried [3] times, each with  maximum [30s] timeout] 
看下服务正常不,超时了,有撒变更没有。
 

etoak

赞同来自:

[2020-05-19T00:13:57,550][INFO ][o.e.c.s.ClusterService   ] [node1] detected_master {node2}{SEviXhshRm2D4gxAvIAGNg}{RaTzomgVSuqkx541eppOig}{192.168.1.88}{192.168.1.88:9305}, added {{node2}{SEviXhshRm2D4gxAvIAGNg}{RaTzomgVSuqkx541eppOig}{192.168.1.88}{192.168.1.88:9305},}, reason: zen-disco-receive(from master [master {node2}{SEviXhshRm2D4gxAvIAGNg}{RaTzomgVSuqkx541eppOig}{192.168.1.88}{192.168.1.88:9305} committed version [1424]])
[2020-05-19T00:14:02,564][INFO ][c.g.g.c.d.KMDictionary   ] 初始化词典!
[2020-05-19T00:15:17,635][INFO ][o.e.m.j.JvmGcMonitorService] [node1] [gc][201] overhead, spent [254ms] collecting in the last [1s]
[2020-05-19T00:16:41,996][INFO ][o.e.m.j.JvmGcMonitorService] [node1] [gc][285] overhead, spent [341ms] collecting in the last [1s]
[2020-05-19T03:06:20,727][INFO ][o.e.d.z.ZenDiscovery     ] [node1] master_left [{node2}{SEviXhshRm2D4gxAvIAGNg}{RaTzomgVSuqkx541eppOig}{192.168.1.88}{192.168.1.88:9305}], reason [failed to ping, tried [3] times, each with  maximum [30s] timeout]
[2020-05-19T03:06:20,732][WARN ][o.e.d.z.ZenDiscovery     ] [node1] master left (reason = failed to ping, tried [3] times, each with  maximum [30s] timeout), current nodes: nodes: 
   {node1}{_EIeKFZNRFOi6LgvpCra6A}{HltU9LBSTWaUwJnM-LnplA}{192.168.0.214}{192.168.0.214:9305}, local
[2020-05-19T03:06:20,734][INFO ][o.e.c.s.ClusterService   ] [node1] removed {{node2}{SEviXhshRm2D4gxAvIAGNg}{RaTzomgVSuqkx541eppOig}{192.168.1.88}{192.168.1.88:9305},}, reason: master_failed ({node2}{SEviXhshRm2D4gxAvIAGNg}{RaTzomgVSuqkx541eppOig}{192.168.1.88}{192.168.1.88:9305})
[2020-05-19T03:08:20,758][WARN ][o.e.d.z.UnicastZenPing   ] [node1] [2] failed send ping to {#zen_unicast_4#}{_GexY1zZSLyFfgf80gTP3g}{192.168.1.88}{192.168.1.88:9305}
java.lang.IllegalStateException: handshake failed with {#zen_unicast_4#}{_GexY1zZSLyFfgf80gTP3g}{192.168.1.88}{192.168.1.88:9305}
    at org.elasticsearch.transport.TransportService.handshake(TransportService.java:370) ~[?:?]
    at org.elasticsearch.transport.TransportService.connectToNodeLightAndHandshake(TransportService.java:345) ~[?:?]
    at org.elasticsearch.transport.TransportService.connectToNodeLightAndHandshake(TransportService.java:319) ~[?:?]
    at org.elasticsearch.discovery.zen.UnicastZenPing$2.run(UnicastZenPing.java:473) [?:?]
    at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:458) [?:?]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131]
    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
Caused by: org.elasticsearch.transport.ReceiveTimeoutTransportException: [][192.168.1.88:9305][internal:transport/handshake] request_id [21878] timed out after [120001ms]
    at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:869) ~[?:?]
    ... 4 more
[2020-05-19T03:08:20,800][INFO ][o.e.c.r.a.AllocationService] [node1] Cluster health status changed from [GREEN] to [YELLOW] (reason: [removed dead nodes on election]).
 

要回复问题请先登录注册