Help understanding hot threads

Elastic Stack Elasticsearch
1

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)

2

Those are thread names, not index names. They are index threads, named numerically.

3

I see, is there a way to tell in ES 2.1 which threads are being consumed by which index?

4

There is not. The threads get shared from a thread pool across all indexing operations.

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.