# Showing all configuration parameters

**URL:** <https://discuss.elastic.co/t/showing-all-configuration-parameters/28863>\
**Category:** Elasticsearch\
**Created:** [September 8, 2015, 6:42pm UTC](https://discuss.elastic.co/t/showing-all-configuration-parameters/28863 "2015-09-08T18:42:28Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmusser](https://avatars.discourse-cdn.com/v4/letter/c/85e7bf/32.png) [@cmusser](https://discuss.elastic.co/u/cmusser)\
**Post date:** [September 8, 2015, 6:42pm UTC](https://discuss.elastic.co/t/showing-all-configuration-parameters/28863/1 "2015-09-08T18:42:28Z")

</div>

How can you dump out all the configured parameters to verify that what's in the configuration file made it into the running system?

I added some new parameters parameters to my Elasticsearch node configuration and I wanted to confirm that they took effect. The parameters are the "routing" ones below:

```
cluster: 
  name: devops-data
  routing:
    allocation:
      disk:
        watermark:
          high: 97%
          low: 95%

```

However, when I tried to query the system for them, they don't show up. The log doesn't show any errors, but the following command doesn't confirm that the settings are in place:

```
me@test:~$ curl 'http://test:9200/_cluster/settings?pretty'
{
  "persistent" : { },
  "transient" : { }
}

```

Is there a more specific command to see the settings?

Chuck

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [September 8, 2015, 6:49pm UTC](https://discuss.elastic.co/t/showing-all-configuration-parameters/28863/2 "2015-09-08T18:49:49Z")

</div>

I don't think there is a way of viewing the effective settings picked up from the config file. Keep in mind that the /\_cluster/settings API only ever shows dynamic settings and never elasticsearch.yml settings, so your check isn't expected to work.

I'd set the disk based allocation watermarks as dynamic settings. Having to do a rolling restart of the cluster just to change that setting doesn't make sense.

---

<div class="post-metadata">

**Author:** ![cmusser](https://avatars.discourse-cdn.com/v4/letter/c/85e7bf/32.png) [@cmusser](https://discuss.elastic.co/u/cmusser)\
**Post date:** [September 8, 2015, 6:53pm UTC](https://discuss.elastic.co/t/showing-all-configuration-parameters/28863/3 "2015-09-08T18:53:03Z")

</div>

OK, understood. In our environment, those parameters are configured via the Puppet module, which writes that configuration file. We don't expect to alter the settings after the fact. So what I'm going to assume is: if there isn't an error in the log, the settings we've defined in the yml file are in effect.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 8, 2015, 8:24pm UTC](https://discuss.elastic.co/t/showing-all-configuration-parameters/28863/4 "2015-09-08T20:24:12Z")

</div>

There's no endpoint that provides the entire config that ES uses, I have a FR for it though so hopefully it'll show up.

---

<div class="post-metadata">

**Author:** ![cmusser](https://avatars.discourse-cdn.com/v4/letter/c/85e7bf/32.png) [@cmusser](https://discuss.elastic.co/u/cmusser)\
**Post date:** [September 8, 2015, 9:07pm UTC](https://discuss.elastic.co/t/showing-all-configuration-parameters/28863/5 "2015-09-08T21:07:03Z")

</div>

That's cool. It would be a nice feature.

---

<div class="post-metadata">

**Author:** ![shanec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shanec/32/4004_2.png) [@shanec](https://discuss.elastic.co/u/shanec)\
**Post date:** [September 8, 2015, 10:11pm UTC](https://discuss.elastic.co/t/showing-all-configuration-parameters/28863/6 "2015-09-08T22:11:45Z")

</div>

FYI, feel free to +1 [https://github.com/elastic/elasticsearch/issues/6732](https://github.com/elastic/elasticsearch/issues/6732) if it looks like it would meet your needs!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 9, 2015, 2:34am UTC](https://discuss.elastic.co/t/showing-all-configuration-parameters/28863/7 "2015-09-09T02:34:43Z")

</div>

Also [https://github.com/elastic/elasticsearch/issues/10713](https://github.com/elastic/elasticsearch/issues/10713)

---

<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, 11:51pm UTC](https://discuss.elastic.co/t/showing-all-configuration-parameters/28863/8 "2017-07-05T23:51:36Z")

</div>