-
Notifications
You must be signed in to change notification settings - Fork 25k
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
java.lang.NullPointerException in Tribe node #20298
Comments
@clintongormley Yes, All nodes are running Version 2.3.4 ,In the tribe node not just request |
@areek could you take a look at this please? |
@zcola Assuming you are running The tribe node keeps track of all the indices for underlying clusters, when you remove or close indices, the cluster state (of the underlying cluster) gets updated and then the tribe node updates its state subsequently. If a
|
Currently, when an index exists in the cluster state but has no shards for reporting stats, the missing stats object cause a `NullPointerException` when requesting the indices stats. In this commit missing stats object for an index are initialized as empty stats instead of null, honoring the stats flags set in the stats request. The commit fixes the issue for all APIs that use the indices stats API namely `_cat/indices`, `_cat/shards` and `_stats`. closes elastic#20298
2.4.4 will still appear, we use "_cat / indices" as node health monitoring |
Currently, when an index exists in the cluster state but has no shards for reporting stats, the missing stats object cause a `NullPointerException` when requesting the indices stats. In this commit missing stats object for an index are initialized as empty stats instead of null, honoring the stats flags set in the stats request. The commit fixes the issue for all APIs that use the indices stats API namely `_cat/indices`, `_cat/shards` and `_stats`. closes elastic#20298
Note that a fix for this issue existed in #20464, but needs to be revived to be mergeable. |
Tribe node was removed in #28443, so this issue is no longer relevant. |
Elasticsearch version:2.3.4
Plugins installed: [ 'analysis-ik', 'kopf', ' license', 'marvel-agent' ]
JVM version:Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
OS version:Debian 8
Description of the problem including expected versus actual behavior:
Steps to reproduce:
19.36
,98.78
error)98.78
back to normalProvide logs (if relevant):
The text was updated successfully, but these errors were encountered: