# Any negative impact of a long discovery.zen.ping\_timeout setting

**URL:** <https://discuss.elastic.co/t/any-negative-impact-of-a-long-discovery-zen-ping-timeout-setting/17916>\
**Category:** Elasticsearch\
**Created:** [June 5, 2014, 2:31am UTC](https://discuss.elastic.co/t/any-negative-impact-of-a-long-discovery-zen-ping-timeout-setting/17916 "2014-06-05T02:31:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeffz](https://avatars.discourse-cdn.com/v4/letter/j/e9c0ed/32.png) [@Jeffz](https://discuss.elastic.co/u/Jeffz)\
**Post date:** [June 5, 2014, 2:31am UTC](https://discuss.elastic.co/t/any-negative-impact-of-a-long-discovery-zen-ping-timeout-setting/17916/1 "2014-06-05T02:31:25Z")

</div>

According to [Zen discovery](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html), the default setting for discovery.zen.ping\_timeout = 3s. For a slow or congested network, higher values assure less chance of failure. If that's case, could we set it a higher value, say = 60s, any negative impact? Thanks in advance for any feedbacks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:24am UTC](https://discuss.elastic.co/t/any-negative-impact-of-a-long-discovery-zen-ping-timeout-setting/17916/2 "2017-07-06T01:24:35Z")

</div>