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

processors setting is not reflected in nodes info API ("os.available_processors") #13917

Closed
FestivalBobcats opened this issue Oct 3, 2015 · 2 comments · Fixed by #14409
Closed

Comments

@FestivalBobcats
Copy link

https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-threadpool.html#processors

The end of that page seems to imply the processors value passed in settings will be displayed in the nodes info API with the os flag. However, it seems to always display information retrieved from the OS.

I know the setting is going through due to the change in thread pool values.

Should the "available_processors" value display what is passed in settings, or is it assumed to be actual OS information?

(on 1.7.1)

@clintongormley clintongormley added discuss :Data Management/Stats Statistics tracking and retrieval APIs labels Oct 3, 2015
@clintongormley
Copy link

I think we should keep the available_processors key as it is today, but that we should include an allocated_processors key which shows actual number of processors that we are using.

@FestivalBobcats
Copy link
Author

Definitely agree with that approach.

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.

3 participants