# Get "Effective" Cluster settings

**URL:** <https://discuss.elastic.co/t/get-effective-cluster-settings/11043>\
**Category:** Elasticsearch\
**Created:** [March 6, 2013, 11:23pm UTC](https://discuss.elastic.co/t/get-effective-cluster-settings/11043 "2013-03-06T23:23:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_smith/32/1323_2.png) [@Paul\_Smith](https://discuss.elastic.co/u/Paul_Smith)\
**Post date:** [March 6, 2013, 11:23pm UTC](https://discuss.elastic.co/t/get-effective-cluster-settings/11043/1 "2013-03-06T23:23:00Z")

</div>

The \_cluster/\_settings API shows all configured settings that are  
overridden, but doesn't show the effective settings of the cluster for  
values tuned via the elasticsearch.yml.

For example, if I configure the concurrent\_streams and max\_size\_per\_sec  
values via the elasticsearch.yml file, and startup the cluster, querying  
the \_cluster/settings end point shows absolutely no values set, because all  
running values are 'pristine' compared to the loaded values.

Programattically though, it would be nicer to be able to see all settings  
values without having to bother hacking into parsing the local  
elasticsearch.yml file to work it out.

Am I missing something? Is there a way to query the cluster to get the  
current running values for ALL settings ?

cheers,

Paul Smith

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![drewr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewr/32/7803_2.png) [@drewr](https://discuss.elastic.co/u/drewr)\
**Post date:** [March 6, 2013, 11:47pm UTC](https://discuss.elastic.co/t/get-effective-cluster-settings/11043/2 "2013-03-06T23:47:37Z")

</div>

Paul Smith wrote:

[...]

> Programattically though, it would be nicer to be able to see all  
> settings values without having to bother hacking into parsing the  
> local elasticsearch.yml file to work it out.
> 
> Am I missing something? Is there a way to query the cluster to get the  
> current running values for ALL settings ?

No, but there should be. We've been talking about this lately  
actually.

> <https://github.com/elastic/elasticsearch/issues/2738>
>
> We should provide an endpoint that dumps a map of all settings and their values.…
> 
> \`\`\`
> % curl localhost:9200/\_config
> {
> "cluster": {
> "name": "elasticsearch"
> }, 
> "index": {
> "number\_of\_shards": 1
> }, 
> "node": {
> "data": true, 
> "master": true
> },
> "etc": "..."
> }
> \`\`\`

-Drew

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 2:47am UTC](https://discuss.elastic.co/t/get-effective-cluster-settings/11043/3 "2017-07-06T02:47:53Z")

</div>