# Help understanding hot threads **URL:** \ **Category:** Elasticsearch\ **Created:** [December 13, 2016, 9:50pm UTC](https://discuss.elastic.co/t/help-understanding-hot-threads/68943 "2016-12-13T21:50:26Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![stecino](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@stecino](https://discuss.elastic.co/u/stecino)\ **Post date:** [December 13, 2016, 9:50pm UTC](https://discuss.elastic.co/t/help-understanding-hot-threads/68943/1 "2016-12-13T21:50:26Z")
I am querying hot threads and I am seeing these index names, is this native to ES? Not sure what that means. By default groovy is turned off, but we have it turned on. Does this mean a client that is using groovy could be triggering this? 22.8% (113.8ms out of 500ms) cpu usage by thread 'elasticsearch[prodserver]**[index][T#11]'** 10/10 snapshots sharing following 20 elements groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:265) groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:254) groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:212) org.elasticsearch.script.groovy.GroovyScriptEngineService.compile(GroovyScriptEngineService.java:143) org.elasticsearch.script.ScriptService.compileInternal(ScriptService.java:311) org.elasticsearch.script.ScriptService.compile(ScriptService.java:257) org.elasticsearch.script.ScriptService.executable(ScriptService.java:442) org.elasticsearch.action.update.UpdateHelper.executeScript(UpdateHelper.java:249) org.elasticsearch.action.update.UpdateHelper.prepare(UpdateHelper.java:196) org.elasticsearch.action.update.UpdateHelper.prepare(UpdateHelper.java:79) org.elasticsearch.action.update.TransportUpdateAction.shardOperation(TransportUpdateAction.java:170) org.elasticsearch.action.update.TransportUpdateAction.shardOperation(TransportUpdateAction.java:164) org.elasticsearch.action.update.TransportUpdateAction.shardOperation(TransportUpdateAction.java:65) org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$ShardTransportHandler.messageReceived(TransportInstanceSingleOperationAction.java:249) org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$ShardTransportHandler.messageReceived(TransportInstanceSingleOperationAction.java:245) org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler.doRun(MessageChannelHandler.java:299) org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) java.lang.Thread.run(Thread.java:745) 19.0% (95.1ms out of 500ms) cpu usage by thread 'elasticsearch[prodserver]**[index][T#18]'** 10/10 snapshots sharing following 16 elements groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:265) groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:254) groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:212) org.elasticsearch.script.groovy.GroovyScriptEngineService.compile(GroovyScriptEngineService.java:143) org.elasticsearch.script.ScriptService.compileInternal(ScriptService.java:311) org.elasticsearch.script.ScriptService.compile(ScriptService.java:257) org.elasticsearch.script.ScriptService.executable(ScriptService.java:442) org.elasticsearch.action.update.UpdateHelper.executeScript(UpdateHelper.java:249) org.elasticsearch.action.update.UpdateHelper.prepare(UpdateHelper.java:196) org.elasticsearch.action.update.UpdateHelper.prepare(UpdateHelper.java:79) ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [December 14, 2016, 4:12am UTC](https://discuss.elastic.co/t/help-understanding-hot-threads/68943/2 "2016-12-14T04:12:08Z")
Those are thread names, not index names. They are index threads, named numerically. ---
**Author:** ![stecino](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@stecino](https://discuss.elastic.co/u/stecino)\ **Post date:** [December 14, 2016, 4:39am UTC](https://discuss.elastic.co/t/help-understanding-hot-threads/68943/3 "2016-12-14T04:39:13Z")
I see, is there a way to tell in ES 2.1 which threads are being consumed by which index? ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [December 14, 2016, 4:49am UTC](https://discuss.elastic.co/t/help-understanding-hot-threads/68943/4 "2016-12-14T04:49:38Z")
There is not. The threads get shared from a thread pool across all indexing operations. ---
**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, 2017, 4:49am UTC](https://discuss.elastic.co/t/help-understanding-hot-threads/68943/5 "2017-01-11T04:49:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.