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

ElasticsearchNodesSniffer complains about "unknown role [ml]" #52864

Closed
bobbyi opened this issue Feb 27, 2020 · 3 comments · Fixed by #52888
Closed

ElasticsearchNodesSniffer complains about "unknown role [ml]" #52864

bobbyi opened this issue Feb 27, 2020 · 3 comments · Fixed by #52888

Comments

@bobbyi
Copy link

bobbyi commented Feb 27, 2020

We have an API server using version 7.5.1 of the elasticsearch-rest-high-level-client and elasticsearch-rest-client-sniffer Java libraries, which matches the version of ES used on our cluster. It is working fine, but our application log ends up filled with messages saying
WARN o.e.c.s.ElasticsearchNodesSniffer - unknown role [ml] on node <name>

I asked about this on the official Elastic forum and was told by David Turner
(an Elastic Team Member) that this behavior is a bug and I should file it here. Specifically, he says "The ElasticsearchNodesSniffer only knows about the three core roles... IOW it was not updated when node roles became pluggable", and points to the code here:

while (parser.nextToken() != JsonToken.END_ARRAY) {
switch (parser.getText()) {
case "master":
master = true;
break;
case "data":
data = true;
break;
case "ingest":
ingest = true;
break;
default:
logger.warn("unknown role [" + parser.getText() + "] on node [" + nodeId + "]");
}

@jasontedor
Copy link
Member

Ouch, that's a bad bug. This relates to #43175 and #45174. I own ensuring this is fixed.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Java High Level REST Client)

@jasontedor
Copy link
Member

I opened #52888.

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

Successfully merging a pull request may close this issue.

3 participants