We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
These two parameters are not serialized (https://github.com/elastic/elasticsearch/blob/master/core/src/main/java/org/elasticsearch/monitor/os/OsInfo.java#L107), although they are build in the json response (https://github.com/elastic/elasticsearch/blob/master/core/src/main/java/org/elasticsearch/monitor/os/OsInfo.java#L82). Consequently, when I start two nodes on one machine I get for one node
"os": { "refresh_interval_in_millis": 1000, "name": "Linux", "arch": "amd64", "version": "3.13.0-39-generic", "available_processors": 12, "allocated_processors": 12 },
and
"os": { "refresh_interval_in_millis": 1000, "available_processors": 12, "allocated_processors": 12 },
for the one that did not handle the request. Is there any reason for it or should I fix it?
The text was updated successfully, but these errors were encountered:
+1 to fix
Sorry, something went wrong.
Seems worth fixing.
serialize os name, arch and version too
0f951a4
These three properties are build in the jason response but were not transported when a node sends the response. closes elastic#15422
7a46953
brwe
No branches or pull requests
These two parameters are not serialized (https://github.com/elastic/elasticsearch/blob/master/core/src/main/java/org/elasticsearch/monitor/os/OsInfo.java#L107), although they are build in the json response (https://github.com/elastic/elasticsearch/blob/master/core/src/main/java/org/elasticsearch/monitor/os/OsInfo.java#L82). Consequently, when I start two nodes on one machine I get for one node
and
for the one that did not handle the request.
Is there any reason for it or should I fix it?
The text was updated successfully, but these errors were encountered: