# Index.refresh\_interval setting in elasticsearch.yml not taking effect

**URL:** <https://discuss.elastic.co/t/index-refresh-interval-setting-in-elasticsearch-yml-not-taking-effect/8349>\
**Category:** Elasticsearch\
**Created:** [July 8, 2012, 4:14pm UTC](https://discuss.elastic.co/t/index-refresh-interval-setting-in-elasticsearch-yml-not-taking-effect/8349 "2012-07-08T16:14:49Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![T\_Vinod\_Gupta](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@T\_Vinod\_Gupta](https://discuss.elastic.co/u/T_Vinod_Gupta)\
**Post date:** [July 8, 2012, 4:14pm UTC](https://discuss.elastic.co/t/index-refresh-interval-setting-in-elasticsearch-yml-not-taking-effect/8349/1 "2012-07-08T16:14:49Z")

</div>

does this look wrong?

elasticsearch.yml:  
index.refresh\_interval: 60s

after i restart ES, it doesnt look like taking effect -  
curl -XGET '[http://localhost:9200/\_cluster/nodes?pretty=true](http://localhost:9200/_cluster/nodes?pretty=true)'  
...  
"os" : {  
"refresh\_interval" : 1000,  
"cpu" : {  
....  
"process" : {  
"refresh\_interval" : 1000,

thanks

---

<div class="post-metadata">

**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\
**Post date:** [July 8, 2012, 5:38pm UTC](https://discuss.elastic.co/t/index-refresh-interval-setting-in-elasticsearch-yml-not-taking-effect/8349/2 "2012-07-08T17:38:53Z")

</div>

These are two different settings. The setting that you set in the config  
file determines how often shards should be automatically refreshed, the  
value that you check by running your request shows how often os stats  
should be updated.

On Sunday, July 8, 2012 12:14:49 PM UTC-4, T Vinod Gupta wrote:

> does this look wrong?
> 
> elasticsearch.yml:  
> index.refresh\_interval: 60s
> 
> after i restart ES, it doesnt look like taking effect -  
> curl -XGET '[http://localhost:9200/\_cluster/nodes?pretty=true](http://localhost:9200/_cluster/nodes?pretty=true)'  
> ...  
> "os" : {  
> "refresh\_interval" : 1000,  
> "cpu" : {  
> ....  
> "process" : {  
> "refresh\_interval" : 1000,
> 
> thanks

---

<div class="post-metadata">

**Author:** ![T\_Vinod\_Gupta](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@T\_Vinod\_Gupta](https://discuss.elastic.co/u/T_Vinod_Gupta)\
**Post date:** [July 8, 2012, 5:56pm UTC](https://discuss.elastic.co/t/index-refresh-interval-setting-in-elasticsearch-yml-not-taking-effect/8349/3 "2012-07-08T17:56:22Z")

</div>

That's what I guessed too. But then /\_settings was also not showing this. Then did a post to \_settings for refresh\_interval. That seemed to reflect in the get call. But then I don't know if this will persist after restart.

Thanks

Sent from my iPhone

On Jul 8, 2012, at 10:38 AM, Igor Motov [imotov@gmail.com](mailto:imotov@gmail.com) wrote:

> These are two different settings. The setting that you set in the config file determines how often shards should be automatically refreshed, the value that you check by running your request shows how often os stats should be updated.
> 
> On Sunday, July 8, 2012 12:14:49 PM UTC-4, T Vinod Gupta wrote:  
> does this look wrong?
> 
> elasticsearch.yml:  
> index.refresh\_interval: 60s
> 
> after i restart ES, it doesnt look like taking effect -  
> curl -XGET '[http://localhost:9200/\_cluster/nodes?pretty=true](http://localhost:9200/_cluster/nodes?pretty=true)'  
> ...  
> "os" : {  
> "refresh\_interval" : 1000,  
> "cpu" : {  
> ....  
> "process" : {  
> "refresh\_interval" : 1000,
> 
> thanks

---

<div class="post-metadata">

**Author:** ![Radu\_Gheorghe1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/radu_gheorghe1/32/2688_2.png) [@Radu\_Gheorghe1](https://discuss.elastic.co/u/Radu_Gheorghe1)\
**Post date:** [July 9, 2012, 6:26am UTC](https://discuss.elastic.co/t/index-refresh-interval-setting-in-elasticsearch-yml-not-taking-effect/8349/4 "2012-07-09T06:26:27Z")

</div>

It does persist after restart.

I think the configuration option you initially wrote will work just fine,  
but I don't know of a way to verify that with the REST API.

I usually change this in a general way by defining an index template in my  
configuration. Take a look here for details:

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

On Sunday, July 8, 2012 8:56:22 PM UTC+3, T Vinod Gupta wrote:

> That's what I guessed too. But then /\_settings was also not showing this.  
> Then did a post to \_settings for refresh\_interval. That seemed to reflect  
> in the get call. But then I don't know if this will persist after restart.
> 
> Thanks
> 
> Sent from my iPhone
> 
> On Jul 8, 2012, at 10:38 AM, Igor Motov \<\> wrote:
> 
> These are two different settings. The setting that you set in the config  
> file determines how often shards should be automatically refreshed, the  
> value that you check by running your request shows how often os stats  
> should be updated.
> 
> On Sunday, July 8, 2012 12:14:49 PM UTC-4, T Vinod Gupta wrote:
> 
> > does this look wrong?
> > 
> > elasticsearch.yml:  
> > index.refresh\_interval: 60s
> > 
> > after i restart ES, it doesnt look like taking effect -  
> > curl -XGET '[http://localhost:9200/\_cluster/nodes?pretty=true](http://localhost:9200/_cluster/nodes?pretty=true)'  
> > ...  
> > "os" : {  
> > "refresh\_interval" : 1000,  
> > "cpu" : {  
> > ....  
> > "process" : {  
> > "refresh\_interval" : 1000,
> > 
> > thanks

---

<div class="post-metadata">

**Author:** ![T\_Vinod\_Gupta](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@T\_Vinod\_Gupta](https://discuss.elastic.co/u/T_Vinod_Gupta)\
**Post date:** [July 9, 2012, 6:33am UTC](https://discuss.elastic.co/t/index-refresh-interval-setting-in-elasticsearch-yml-not-taking-effect/8349/5 "2012-07-09T06:33:54Z")

</div>

Thanks, I did see it getting persisted after restart.

You also asked me to check out bigdesk. I was finally able to do so.. So  
what are the typical things that should alarm me? somethings that stand out  
in my case -

1. open transport channels = 231. seems high
2. threads count = 85-105 range.. seems high. peak = 125
3. fields cache size = 168mb, filter cache size = 37mb. doesnt look bad.

thanks

On Sun, Jul 8, 2012 at 11:26 PM, Radu Gheorghe [radu0gheorghe@gmail.com](mailto:radu0gheorghe@gmail.com)wrote:

> It does persist after restart.
> 
> I think the configuration option you initially wrote will work just fine,  
> but I don't know of a way to verify that with the REST API.
> 
> I usually change this in a general way by defining an index template in my  
> configuration. Take a look here for details:
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-templates.html)
> 
> On Sunday, July 8, 2012 8:56:22 PM UTC+3, T Vinod Gupta wrote:
> 
> > That's what I guessed too. But then /\_settings was also not showing this.  
> > Then did a post to \_settings for refresh\_interval. That seemed to reflect  
> > in the get call. But then I don't know if this will persist after restart.
> > 
> > Thanks
> > 
> > Sent from my iPhone
> > 
> > On Jul 8, 2012, at 10:38 AM, Igor Motov \<\> wrote:
> > 
> > These are two different settings. The setting that you set in the config  
> > file determines how often shards should be automatically refreshed, the  
> > value that you check by running your request shows how often os stats  
> > should be updated.
> > 
> > On Sunday, July 8, 2012 12:14:49 PM UTC-4, T Vinod Gupta wrote:
> > 
> > > does this look wrong?
> > > 
> > > elasticsearch.yml:  
> > > index.refresh\_interval: 60s
> > > 
> > > after i restart ES, it doesnt look like taking effect -  
> > > curl -XGET '[http://localhost:9200/\_\*\*cluster/nodes?pretty=true](http://localhost:9200/_**cluster/nodes?pretty=true)[http://localhost:9200/\_cluster/nodes?pretty=true](http://localhost:9200/_cluster/nodes?pretty=true)  
> > > '  
> > > ...  
> > > "os" : {  
> > > "refresh\_interval" : 1000,  
> > > "cpu" : {  
> > > ....  
> > > "process" : {  
> > > "refresh\_interval" : 1000,
> > > 
> > > thanks

---

<div class="post-metadata">

**Author:** ![Radu\_Gheorghe1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/radu_gheorghe1/32/2688_2.png) [@Radu\_Gheorghe1](https://discuss.elastic.co/u/Radu_Gheorghe1)\
**Post date:** [July 10, 2012, 4:56am UTC](https://discuss.elastic.co/t/index-refresh-interval-setting-in-elasticsearch-yml-not-taking-effect/8349/6 "2012-07-10T04:56:57Z")

</div>

I don't know, I would have guessed that if you have spikes in your query  
times you would see the same spikes in BigDesk somewhere...

Isn't that the case?

luni, 9 iulie 2012, 09:33:54 UTC+3, T Vinod Gupta a scris:

> Thanks, I did see it getting persisted after restart.
> 
> You also asked me to check out bigdesk. I was finally able to do so.. So  
> what are the typical things that should alarm me? somethings that stand out  
> in my case -
> 
> 1. open transport channels = 231. seems high
> 2. threads count = 85-105 range.. seems high. peak = 125
> 3. fields cache size = 168mb, filter cache size = 37mb. doesnt look bad.
> 
> thanks
> 
> On Sun, Jul 8, 2012 at 11:26 PM, Radu Gheorghe \<\> wrote:
> 
> > It does persist after restart.
> > 
> > I think the configuration option you initially wrote will work just fine,  
> > but I don't know of a way to verify that with the REST API.
> > 
> > I usually change this in a general way by defining an index template in  
> > my configuration. Take a look here for details:
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-templates.html)
> > 
> > On Sunday, July 8, 2012 8:56:22 PM UTC+3, T Vinod Gupta wrote:
> > 
> > > That's what I guessed too. But then /\_settings was also not showing  
> > > this. Then did a post to \_settings for refresh\_interval. That seemed to  
> > > reflect in the get call. But then I don't know if this will persist after  
> > > restart.
> > > 
> > > Thanks
> > > 
> > > Sent from my iPhone
> > > 
> > > On Jul 8, 2012, at 10:38 AM, Igor Motov \<\> wrote:
> > > 
> > > These are two different settings. The setting that you set in the config  
> > > file determines how often shards should be automatically refreshed, the  
> > > value that you check by running your request shows how often os stats  
> > > should be updated.
> > > 
> > > On Sunday, July 8, 2012 12:14:49 PM UTC-4, T Vinod Gupta wrote:
> > > 
> > > > does this look wrong?
> > > > 
> > > > elasticsearch.yml:  
> > > > index.refresh\_interval: 60s
> > > > 
> > > > after i restart ES, it doesnt look like taking effect -  
> > > > curl -XGET '[http://localhost:9200/\_\*\*cluster/nodes?pretty=true](http://localhost:9200/_**cluster/nodes?pretty=true)[http://localhost:9200/\_cluster/nodes?pretty=true](http://localhost:9200/_cluster/nodes?pretty=true)  
> > > > '  
> > > > ...  
> > > > "os" : {  
> > > > "refresh\_interval" : 1000,  
> > > > "cpu" : {  
> > > > ....  
> > > > "process" : {  
> > > > "refresh\_interval" : 1000,
> > > > 
> > > > thanks

---

<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, 3:20am UTC](https://discuss.elastic.co/t/index-refresh-interval-setting-in-elasticsearch-yml-not-taking-effect/8349/7 "2017-07-06T03:20:49Z")

</div>


