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.

Sign up for GitHub

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

Jump to bottom

HotThreads fail with AIOOB if busiestThreads > actual threads #4927

Closed
s1monw opened this issue Jan 28, 2014 · 0 comments · Fixed by #4928
Closed

HotThreads fail with AIOOB if busiestThreads > actual threads #4927

s1monw opened this issue Jan 28, 2014 · 0 comments · Fixed by #4928
Assignees
@s1monw
Labels
>bug v0.90.11 v1.0.0.RC2 v1.1.0 v2.0.0-beta1

Comments

@s1monw
Copy link
Contributor

s1monw commented Jan 28, 2014

we currently use the number of hot threads that we are interested in as the value for iterating over the actual hot threads which can lead to AIOOB is the actual number of threads is less than the given number.

which will result in an exception like this:

Caused by: java.lang.IndexOutOfBoundsException: Index: 93, Size: 93
    at java.util.ArrayList.RangeCheck(ArrayList.java:547)
    at java.util.ArrayList.get(ArrayList.java:322)
    at org.elasticsearch.monitor.jvm.HotThreads.innerDetect(HotThreads.java:149)
    at org.elasticsearch.monitor.jvm.HotThreads.detect(HotThreads.java:75)
    at org.elasticsearch.action.admin.cluster.node.hotthreads.TransportNodesHotThreadsAction.nodeOperation(TransportNodesHotThreadsAction.java:101)
    ... 5 more
@ghost ghost assigned s1monw Jan 28, 2014
@s1monw s1monw mentioned this issue Jan 28, 2014
Merged
s1monw added a commit that referenced this issue Jan 28, 2014
@s1monw
Use num of actual threads if busiestThreads is larger
f9060f6 
We currently use the number of hot threads that we are
interested in as the value for iterating over the actual
hot threads which can lead to AIOOB is the actual number
of threads is less than the given number.

Closes #4927
s1monw added a commit that referenced this issue Jan 28, 2014
@s1monw
Use num of actual threads if busiestThreads is larger
f61cd56 
We currently use the number of hot threads that we are
interested in as the value for iterating over the actual
hot threads which can lead to AIOOB is the actual number
of threads is less than the given number.

Closes #4927
s1monw added a commit that referenced this issue Jan 28, 2014
@s1monw
Use num of actual threads if busiestThreads is larger
c804824 
We currently use the number of hot threads that we are
interested in as the value for iterating over the actual
hot threads which can lead to AIOOB is the actual number
of threads is less than the given number.

Closes #4927
@s1monw s1monw closed this as completed in 25f0bba Jan 28, 2014
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@s1monw
Use num of actual threads if busiestThreads is larger
94009cf 
We currently use the number of hot threads that we are
interested in as the value for iterating over the actual
hot threads which can lead to AIOOB is the actual number
of threads is less than the given number.

Closes elastic#4927
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@s1monw
Use num of actual threads if busiestThreads is larger
f5c292e 
We currently use the number of hot threads that we are
interested in as the value for iterating over the actual
hot threads which can lead to AIOOB is the actual number
of threads is less than the given number.

Closes elastic#4927
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@s1monw s1monw

Labels
>bug v0.90.11 v1.0.0.RC2 v1.1.0 v2.0.0-beta1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use num of actual threads if busiestThreads is larger s1monw/elasticsearch
1 participant
@s1monw