Skip to content

node info does not contain os arch and name #15422

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

Closed
brwe opened this issue Dec 14, 2015 · 2 comments
Closed

node info does not contain os arch and name #15422

brwe opened this issue Dec 14, 2015 · 2 comments
Assignees
Labels
>bug :Data Management/Stats Statistics tracking and retrieval APIs v2.2.0

Comments

@brwe
Copy link
Contributor

brwe commented Dec 14, 2015

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?

@jpountz
Copy link
Contributor

jpountz commented Dec 14, 2015

+1 to fix

@nik9000
Copy link
Member

nik9000 commented Dec 14, 2015

Seems worth fixing.

@clintongormley clintongormley added >bug :Data Management/Stats Statistics tracking and retrieval APIs labels Dec 14, 2015
@brwe brwe added the v2.2.0 label Dec 15, 2015
brwe added a commit to brwe/elasticsearch that referenced this issue Dec 15, 2015
These three properties are build in the jason response but were not
transported when a node sends the response.

closes elastic#15422
@brwe brwe closed this as completed in 7a46953 Dec 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Data Management/Stats Statistics tracking and retrieval APIs v2.2.0
Projects
None yet
Development

No branches or pull requests

4 participants