-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[Transform] Possible NPE in usage endpoint #48734
Labels
Comments
Pinging @elastic/ml-core (:ml/Transform) |
Another occurrence after transform has been disabled on a subset of nodes.
|
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Feb 28, 2020
hendrikmuhs
pushed a commit
that referenced
this issue
Mar 2, 2020
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Mar 2, 2020
…odes and test which nodes are allowed to do remote connections closes elastic#52200 closes elastic#50033 closes elastic#48734
hendrikmuhs
pushed a commit
that referenced
this issue
Mar 2, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This has been reported on a 7.3 installation:
First investigation:
The stack points to:
https://github.com/elastic/elasticsearch/blob/7.3/x-pack/plugin/data-frame/src/main/java/org/elasticsearch/xpack/dataframe/DataFrameFeatureSet.java#L120
taskState
seems to benull
, which is strange, because there is no place it's set tonull
. My best guess at the moment:https://github.com/elastic/elasticsearch/blob/7.3/x-pack/plugin/data-frame/src/main/java/org/elasticsearch/xpack/dataframe/transforms/DataFrameTransformTask.java#L100
This set's the taskState from a previous State which is loaded from the internal index. The state document is loaded in a lenient fashion, so I can only imagine that this got somehow corrupted and the task state got set to
null
at the above place.Solution
It's hard to find a definitive fix as a lot of changes happened between 7.3 and now. Its also not clear how to reproduce the problem. Nevertheless based on the assumptions made we should harden the code and make it robust against potential corruption.
The text was updated successfully, but these errors were encountered: