# BUG: Negative value is successfully set for "discovery.zen.commit\_timeout" parameter

**URL:** <https://discuss.elastic.co/t/bug-negative-value-is-successfully-set-for-discovery-zen-commit-timeout-parameter/159692>\
**Category:** Elasticsearch\
**Created:** [December 6, 2018, 9:18am UTC](https://discuss.elastic.co/t/bug-negative-value-is-successfully-set-for-discovery-zen-commit-timeout-parameter/159692 "2018-12-06T09:18:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikhil.k](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@nikhil.k](https://discuss.elastic.co/u/nikhil.k)\
**Post date:** [December 6, 2018, 9:18am UTC](https://discuss.elastic.co/t/bug-negative-value-is-successfully-set-for-discovery-zen-commit-timeout-parameter/159692/1 "2018-12-06T09:18:04Z")

</div>

Hi Everyone,

Elasticsearch Version: 5.5

I am able to successfully set the negative value of "discovery.zen.commit\_timeout" parameter in elasticsearch.yml or when it's value is changed dynamically by using the cluster update settings API.

Whereas an error is shown on the console when "discovery.zen.publish\_timeout" parameter is set to negative value.

> > Failed to parse value [-10s] for setting [discovery.zen.publish\_timeout] must be \>= 0s (Debug Log)

Why the value of "discovery.zen.commit\_timeout" parameter can be set to negative value?

Can anyone also tell what will be value of "discovery.zen.commit\_timeout" parameter when it successfully set to negative value (let say, -10s). Is it still set to default "30s" value?

Regards  
Nikhil Kapoor

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 6, 2018, 12:24pm UTC](https://discuss.elastic.co/t/bug-negative-value-is-successfully-set-for-discovery-zen-commit-timeout-parameter/159692/2 "2018-12-06T12:24:37Z")

</div>

Thanks @nikhil.k. This looks to have been the situation for a very long time, and these parameters are expected to see a bit of an overhaul in 7.0 so this issue will not apply any more. For now, if you set it to a negative value it's treated like zero, i.e. an immediate timeout.

It's not recommended to change these settings from their defaults, as this can cause cluster instability.

---

<div class="post-metadata">

**Author:** ![nikhil.k](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@nikhil.k](https://discuss.elastic.co/u/nikhil.k)\
**Post date:** [December 14, 2018, 9:09am UTC](https://discuss.elastic.co/t/bug-negative-value-is-successfully-set-for-discovery-zen-commit-timeout-parameter/159692/3 "2018-12-14T09:09:44Z")

</div>

Hi @DavidTurner

I have filed this bug in the github:

> <https://github.com/elastic/elasticsearch/issues/36632>

Regards  
Nikhil Kapoor

---

<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:** [January 11, 2019, 9:09am UTC](https://discuss.elastic.co/t/bug-negative-value-is-successfully-set-for-discovery-zen-commit-timeout-parameter/159692/4 "2019-01-11T09:09:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.