Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to detect hot threads #4775

Closed
nik9000 opened this issue Jan 17, 2014 · 2 comments · Fixed by #4777
Closed

Failed to detect hot threads #4775

nik9000 opened this issue Jan 17, 2014 · 2 comments · Fixed by #4777

Comments

@nik9000
Copy link
Member

nik9000 commented Jan 17, 2014

I'm not really sure what caused this but I'm pretty sure I didn't get hot threads from the node it mentions:

[2014-01-17 01:36:11,648][DEBUG][action.admin.cluster.node.hotthreads] [elastic1008] failed to execute on node [Orfebp5QSN2iIag5IKTrXg]
org.elasticsearch.transport.RemoteTransportException: [elastic1001][inet[/10.64.0.108:9300]][cluster/nodes/hot_threads/n]
Caused by: org.elasticsearch.ElasticSearchException: failed to detect hot threads
        at org.elasticsearch.action.admin.cluster.node.hotthreads.TransportNodesHotThreadsAction.nodeOperation(TransportNodesHotThreadsAction.java:103)
        at org.elasticsearch.action.admin.cluster.node.hotthreads.TransportNodesHotThreadsAction.nodeOperation(TransportNodesHotThreadsAction.java:43)
        at org.elasticsearch.action.support.nodes.TransportNodesOperationAction$NodeTransportHandler.messageReceived(TransportNodesOperationAction.java:281)
        at org.elasticsearch.action.support.nodes.TransportNodesOperationAction$NodeTransportHandler.messageReceived(TransportNodesOperationAction.java:272)
        at org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler.run(MessageChannelHandler.java:270)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:724)
Caused by: java.lang.NullPointerException
        at org.elasticsearch.monitor.jvm.HotThreads.similarity(HotThreads.java:216)
        at org.elasticsearch.monitor.jvm.HotThreads.innerDetect(HotThreads.java:177)
        at org.elasticsearch.monitor.jvm.HotThreads.detect(HotThreads.java:75)
        at org.elasticsearch.action.admin.cluster.node.hotthreads.TransportNodesHotThreadsAction.nodeOperation(TransportNodesHotThreadsAction.java:101)
        ... 7 more
@ghost ghost assigned s1monw Jan 17, 2014
s1monw added a commit that referenced this issue Jan 17, 2014
If a thread is not alive getting ThreadMXBean#getThreadInfo(long[], int)
places null elemnents in the returned array which are not repected
in the HotTheards API.

Closes #4775
@s1monw s1monw closed this as completed in 42377db Jan 17, 2014
@nik9000
Copy link
Member Author

nik9000 commented Jan 17, 2014

Thanks!

@s1monw
Copy link
Contributor

s1monw commented Jan 17, 2014

thank you!

brusic pushed a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014
If a thread is not alive getting ThreadMXBean#getThreadInfo(long[], int)
places null elemnents in the returned array which are not repected
in the HotTheards API.

Closes elastic#4775
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
If a thread is not alive getting ThreadMXBean#getThreadInfo(long[], int)
places null elemnents in the returned array which are not repected
in the HotTheards API.

Closes elastic#4775
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants