# \[WARN \]\[o.e.t.TransportService \] \[esm3\] Received response for a request that has timed out, sent \[33470ms\] ago, timed out \[3470ms\] ago, action \[internal:discovery/zen/fd/master\_ping\] **URL:** \ **Category:** Elasticsearch\ **Created:** [February 23, 2018, 4:06am UTC](https://discuss.elastic.co/t/warn-o-e-t-transportservice-esm3-received-response-for-a-request-that-has-timed-out-sent-33470ms-ago-timed-out-3470ms-ago-action-internal-discovery-zen-fd-master-ping/121158 "2018-02-23T04:06:29Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [February 23, 2018, 4:06am UTC](https://discuss.elastic.co/t/warn-o-e-t-transportservice-esm3-received-response-for-a-request-that-has-timed-out-sent-33470ms-ago-timed-out-3470ms-ago-action-internal-discovery-zen-fd-master-ping/121158/1 "2018-02-23T04:06:30Z")
Hello, I'm running 3 master eligible nodes and every now and then, I get following messages in elasticsearch's log: > esm3 | [2018-02-23T02:36:17,666][WARN][o.e.t.TransportService] [esm3] Received response for a request that has timed out, sent [33470ms] ago, timed out [3470ms] ago, action [internal:discovery/zen/fd/master\_ping], node [{esm1}..... Is there anything I can do to make it better somehow? Please advise. ---
**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:** [February 23, 2018, 7:31am UTC](https://discuss.elastic.co/t/warn-o-e-t-transportservice-esm3-received-response-for-a-request-that-has-timed-out-sent-33470ms-ago-timed-out-3470ms-ago-action-internal-discovery-zen-fd-master-ping/121158/2 "2018-02-23T07:31:13Z")
Is the cluster under heavy load? Is there anything in logs on the elected master node, e.g. warnings about long GC? Where is the cluster deployed? Have you seen any network issues between the nodes? ---
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [February 23, 2018, 4:33pm UTC](https://discuss.elastic.co/t/warn-o-e-t-transportservice-esm3-received-response-for-a-request-that-has-timed-out-sent-33470ms-ago-timed-out-3470ms-ago-action-internal-discovery-zen-fd-master-ping/121158/3 "2018-02-23T16:33:49Z")
under heavy load - yes and no) I, (thought) I stopped all of my apps from writing to elasticsearch as I was updating it from 6.2.1 to 6.2.2... after a while master node was elected, no issues other than the one I mentioned, I do see these as well: > esm1 | [2018-02-23T16:22:51,187][INFO][o.e.m.j.JvmGcMonitorService] [esm1] [gc][47757] overhead, spent [264ms] collecting in the last [1s] all elasticsearch nodes (cluster) are at Google Cloud Platform (Compute Engine). I did not notice any network issues between nodes (all nodes are part of same network). * * * I also noticed following as well: ``` esm1 | [2018-02-23T14:59:02,410][INFO][o.e.m.j.JvmGcMonitorService] [esm1] [gc][42734] overhead, spent [263ms] collecting in the last [1s] esm1 | [2018-02-23T15:15:39,597][INFO][o.e.c.s.MasterService] [esm1] zen-disco-node-left({esc3}{G5HTaP8RQBWcNS-9QPX57Q}{kZ8mKLRrQTSWx9l1BYiWaQ}{10.0.0.238}{10.0.0.238:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true}), reason(left)[{esc3}{G5HTaP8RQBWcNS-9QPX57Q}{kZ8mKLRrQTSWx9l1BYiWaQ}{10.0.0.238}{10.0.0.238:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true} left], reason: removed {{esc3}{G5HTaP8RQBWcNS-9QPX57Q}{kZ8mKLRrQTSWx9l1BYiWaQ}{10.0.0.238}{10.0.0.238:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true},} esm1 | [2018-02-23T15:15:39,676][INFO][o.e.c.s.ClusterApplierService] [esm1] removed {{esc3}{G5HTaP8RQBWcNS-9QPX57Q}{kZ8mKLRrQTSWx9l1BYiWaQ}{10.0.0.238}{10.0.0.238:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true},}, reason: apply cluster state (from master [master {esm1}{LM1Whu2_RyaGBk-vK2A9Eg}{LW0TNipgQECec2V7gXSwBA}{10.0.0.234}{10.0.0.234:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true} committed version [11380] source [zen-disco-node-left({esc3}{G5HTaP8RQBWcNS-9QPX57Q}{kZ8mKLRrQTSWx9l1BYiWaQ}{10.0.0.238}{10.0.0.238:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true}), reason(left)[{esc3}{G5HTaP8RQBWcNS-9QPX57Q}{kZ8mKLRrQTSWx9l1BYiWaQ}{10.0.0.238}{10.0.0.238:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true} left]]]) esm1 | [2018-02-23T15:18:54,001][INFO][o.e.c.s.MasterService] [esm1] zen-disco-node-join[{esc3}{nR9iRdk0TZeQ9a0IPZerhQ}{cXjqWITURtCm2xS4KFguGA}{10.0.0.17}{10.0.0.17:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true}], reason: added {{esc3}{nR9iRdk0TZeQ9a0IPZerhQ}{cXjqWITURtCm2xS4KFguGA}{10.0.0.17}{10.0.0.17:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true},} esm1 | [2018-02-23T15:18:59,353][INFO][o.e.c.s.ClusterApplierService] [esm1] added {{esc3}{nR9iRdk0TZeQ9a0IPZerhQ}{cXjqWITURtCm2xS4KFguGA}{10.0.0.17}{10.0.0.17:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true},}, reason: apply cluster state (from master [master {esm1}{LM1Whu2_RyaGBk-vK2A9Eg}{LW0TNipgQECec2V7gXSwBA}{10.0.0.234}{10.0.0.234:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true} committed version [11382] source [zen-disco-node-join[{esc3}{nR9iRdk0TZeQ9a0IPZerhQ}{cXjqWITURtCm2xS4KFguGA}{10.0.0.17}{10.0.0.17:9300}{ml.machine_memory=7847518208, ml.max_open_jobs=20, ml.enabled=true}]]]) esm1 | [2018-02-23T15:19:32,938][INFO][o.e.c.m.MetaDataMappingService] [esm1] [logstash-2018.02.23/l2maaiOWQBSf08rqEg-icg] update_mapping [doc] ``` and this (master node): ![JVM_Heap_(GB)](https://us1.discourse-cdn.com/elastic/original/3X/0/9/09ed2d81dcf2de84e9418ed719c028c89b5b6d1c.png) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 23, 2018, 4:34pm UTC](https://discuss.elastic.co/t/warn-o-e-t-transportservice-esm3-received-response-for-a-request-that-has-timed-out-sent-33470ms-ago-timed-out-3470ms-ago-action-internal-discovery-zen-fd-master-ping/121158/4 "2018-03-23T16:34:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.