# How to checkout the Discovery Zen settings?

**URL:** <https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087>\
**Category:** Elasticsearch\
**Created:** [August 3, 2016, 9:55am UTC](https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087 "2016-08-03T09:55:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![drjz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drjz/32/972_2.png) [@drjz](https://discuss.elastic.co/u/drjz)\
**Post date:** [August 3, 2016, 9:55am UTC](https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087/1 "2016-08-03T09:55:11Z")

</div>

I've update the Discovery Zen settings to increase the ping\_timeout as explained here: [https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-zen.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-zen.html)

\_cluster/settings  
{  
"persistent" : {  
"discovery.zen.fd.ping\_timeout": "600s"  
}  
}

However, I do not see the updated settings when I get the cluster settings. How can I retrieve these settings, so I know it has correctly been updated?

---

<div class="post-metadata">

**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:** [August 3, 2016, 10:17am UTC](https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087/2 "2016-08-03T10:17:36Z")

</div>

Why are you updating it to such a large value?

---

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [August 3, 2016, 10:23am UTC](https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087/3 "2016-08-03T10:23:51Z")

</div>

Hi,

I just checked this on our upcoming 5.0 release which has reworked the way settings updates are validated and trying to update that setting there results in an error message saying that [discovery.zen.fd.ping\_timeout] is not dynamically updateable. We don't do this kind of settings validation on 1.x and 2.x yet so if you try to update a non updateable setting you unfortunately don't get an error. Its just silently ignored. If you don't see the updated settings in the response chances are they have not been applied.

Christoph

---

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [August 3, 2016, 10:44am UTC](https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087/4 "2016-08-03T10:44:00Z")

</div>

When trying this on any 2.x version of ES you should get a warning in the logs like `[WARN][action.admin.cluster.settings] [Anything] ignoring persistent setting [discovery.zen.fd.ping_timeout], not dynamically updateable`

---

<div class="post-metadata">

**Author:** ![drjz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drjz/32/972_2.png) [@drjz](https://discuss.elastic.co/u/drjz)\
**Post date:** [August 3, 2016, 10:46am UTC](https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087/5 "2016-08-03T10:46:18Z")

</div>

The reason is because our NAS shared storage solution (yes, I am also banging my head against the wall) sometimes gives timeouts after more than 30 seconds, and I do not want nodes to leave the cluster yet, but give it more time (a few minutes), so existing processes like indexing do not immediately quit.

---

<div class="post-metadata">

**Author:** ![drjz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drjz/32/972_2.png) [@drjz](https://discuss.elastic.co/u/drjz)\
**Post date:** [August 3, 2016, 10:47am UTC](https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087/6 "2016-08-03T10:47:25Z")

</div>

Thanks, I have not checked the logs yet. So the only solution would be to manually update this setting in the YML file for each node.

---

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [August 3, 2016, 10:48am UTC](https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087/7 "2016-08-03T10:48:46Z")

</div>

I think so, yes.

---

<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 5, 2017, 10:30pm UTC](https://discuss.elastic.co/t/how-to-checkout-the-discovery-zen-settings/57087/8 "2017-07-05T22:30:27Z")

</div>