version: 6.2.2
[2019-01-21T12:02:02,098][INFO ][o.e.m.j.JvmGcMonitorService] [node-142] [gc][407049] overhead, spent [427ms] collecting in the last [1s]
[2019-01-21T12:02:03,483][INFO ][o.e.m.j.JvmGcMonitorService] [node-142] [gc][407050] overhead, spent [439ms] collecting in the last [1.3s]
[2019-01-21T12:02:05,484][INFO ][o.e.m.j.JvmGcMonitorService] [node-142] [gc][407052] overhead, spent [354ms] collecting in the last [1s]
...(other RemoteTransportException)
[2019-01-21T12:08:18,972][INFO ][o.e.c.r.a.AllocationService] [node-142] Cluster health status changed from [GREEN] to [YELLOW] (reason: [shards failed [[celery_log][0]] ...]).
[2019-01-21T12:08:19,003][WARN ][o.e.d.z.ZenDiscovery ] [node-142] zen-disco-failed-to-publish, current nodes: nodes:
{node-143}{gIvN8KNiQsmY2Lsy20Expg}{TUXpFaUnRTKAa5Asdf19gA}{192.168.30.143}{192.168.30.143:2810}
{node-141}{3kWs-rFaR_yZVZOpRp1BFA}{nFj2LpDWS6qNIeEUKzpBLA}{192.168.30.141}{192.168.30.141:2810}
{node-142}{aYMFcfn3RvKDVfgncxC8cQ}{yodrtCrKSaWcVI49NE9dCg}{192.168.30.142}{192.168.30.142:2810}, local, master
in my config(Elasticsearch.yml),
discovery.zen.fd.ping_interval: 10s
discovery.zen.fd.ping_timeout: 60s
discovery.zen.fd.ping_retries: 3
ping_timeout=60s, ping_retries=3, so when 3 time gc(12:02:05), there will be some wrong, 3mins or later, (12:08:19), send zen-disco-failed-to-publish logs.
this thing always happens, once or twice per day on average.