# After bulk indexing with refresh\_interval disabled, now at 100% CPU usage for \> 24 hours **URL:** \ **Category:** Elasticsearch\ **Created:** [March 7, 2014, 5:58am UTC](https://discuss.elastic.co/t/after-bulk-indexing-with-refresh-interval-disabled-now-at-100-cpu-usage-for-24-hours/16218 "2014-03-07T05:58:04Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Swaroop\_CH](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@Swaroop\_CH](https://discuss.elastic.co/u/Swaroop_CH)\ **Post date:** [March 7, 2014, 5:58am UTC](https://discuss.elastic.co/t/after-bulk-indexing-with-refresh-interval-disabled-now-at-100-cpu-usage-for-24-hours/16218/1 "2014-03-07T05:58:04Z")
Hello, We have a brand-new ES 1.0.1 cluster of 3 m2.xlarge machines, we set `index.refresh_interval` to -1, `index.number_of_replicas` to 0, `index.number_of_shards` to 10 and indexed about half a million documents in about 2000 indexes, this completed successfully in about 10 hours. However, after the bulk indexing completed, I set `index.refresh_interval` to 5, and there is 100% CPU usage in 1 out of the 2 CPUs on all the 3 nodes, and it has been more than 24 hours and it is still at 100% CPU (1 out of 2 CPUs). Is this normal and expected? (Note that the cluster status is green) From `/_nodes/hot_threads`, I can see that `org.elasticsearch.index.shard.service.InternalIndexShard$EngineRefresher.run(InternalIndexShard.java:914)` is what is taking up the CPU. Any advice on the same is welcome. Thank you. Regards, Swaroop -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1371391394171884%40web12m.yandex.ru](https://groups.google.com/d/msgid/elasticsearch/1371391394171884%40web12m.yandex.ru). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Swaroop\_CH](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@Swaroop\_CH](https://discuss.elastic.co/u/Swaroop_CH)\ **Post date:** [March 7, 2014, 6:05am UTC](https://discuss.elastic.co/t/after-bulk-indexing-with-refresh-interval-disabled-now-at-100-cpu-usage-for-24-hours/16218/2 "2014-03-07T06:05:29Z")
For posterity note, the problem was solved by specifying {"index.refresh\_interval": "5s"} - note the "s" : by specifying just "5", ES assumes 5 milliseconds! Regards, Swaroop 07.03.2014, 11:28, "Swaroop CH" [swaroopch@yandex.com](mailto:swaroopch@yandex.com): > Hello, > > We have a brand-new ES 1.0.1 cluster of 3 m2.xlarge machines, we set `index.refresh_interval` to -1, `index.number_of_replicas` to 0, `index.number_of_shards` to 10 and indexed about half a million documents in about 2000 indexes, this completed successfully in about 10 hours. > > However, after the bulk indexing completed, I set `index.refresh_interval` to 5, and there is 100% CPU usage in 1 out of the 2 CPUs on all the 3 nodes, and it has been more than 24 hours and it is still at 100% CPU (1 out of 2 CPUs). Is this normal and expected? (Note that the cluster status is green) > > From `/_nodes/hot_threads`, I can see that `org.elasticsearch.index.shard.service.InternalIndexShard$EngineRefresher.run(InternalIndexShard.java:914)` is what is taking up the CPU. > > Any advice on the same is welcome. > > Thank you. > > Regards, > Swaroop > > -- > 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). > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1371391394171884%40web12m.yandex.ru](https://groups.google.com/d/msgid/elasticsearch/1371391394171884%40web12m.yandex.ru). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1411101394172329%40web12m.yandex.ru](https://groups.google.com/d/msgid/elasticsearch/1411101394172329%40web12m.yandex.ru). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 7, 2014, 7:01am UTC](https://discuss.elastic.co/t/after-bulk-indexing-with-refresh-interval-disabled-now-at-100-cpu-usage-for-24-hours/16218/3 "2014-03-07T07:01:24Z")
I'm sometimes doing the same error with JVM memory parameters. -Xmx512 -Xms512 definitely does not give enough memory to elasticsearch! 🙂 -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 7 mars 2014 à 07:05, Swaroop CH [swaroopch@yandex.com](mailto:swaroopch@yandex.com) a écrit : For posterity note, the problem was solved by specifying {"index.refresh\_interval": "5s"} - note the "s" : by specifying just "5", ES assumes 5 milliseconds! Regards, Swaroop 07.03.2014, 11:28, "Swaroop CH" [swaroopch@yandex.com](mailto:swaroopch@yandex.com): > Hello, > > We have a brand-new ES 1.0.1 cluster of 3 m2.xlarge machines, we set `index.refresh_interval` to -1, `index.number_of_replicas` to 0, `index.number_of_shards` to 10 and indexed about half a million documents in about 2000 indexes, this completed successfully in about 10 hours. > > However, after the bulk indexing completed, I set `index.refresh_interval` to 5, and there is 100% CPU usage in 1 out of the 2 CPUs on all the 3 nodes, and it has been more than 24 hours and it is still at 100% CPU (1 out of 2 CPUs). Is this normal and expected? (Note that the cluster status is green) > > From `/_nodes/hot_threads`, I can see that `org.elasticsearch.index.shard.service.InternalIndexShard$EngineRefresher.run(InternalIndexShard.java:914)` is what is taking up the CPU. > > Any advice on the same is welcome. > > Thank you. > > Regards, > Swaroop > > -- > 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). > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1371391394171884%40web12m.yandex.ru](https://groups.google.com/d/msgid/elasticsearch/1371391394171884%40web12m.yandex.ru). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1411101394172329%40web12m.yandex.ru](https://groups.google.com/d/msgid/elasticsearch/1411101394172329%40web12m.yandex.ru). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/012D35F8-C790-4E57-BBF8-AAABD82C73F2%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/012D35F8-C790-4E57-BBF8-AAABD82C73F2%40pilato.fr). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:45am UTC](https://discuss.elastic.co/t/after-bulk-indexing-with-refresh-interval-disabled-now-at-100-cpu-usage-for-24-hours/16218/4 "2017-07-06T01:45:08Z")