-
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] stats can return old state information if security is enabled #51728
Labels
Comments
Pinging @elastic/ml-core (:ml/Transform) |
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Jan 31, 2020
instead of using the calling user which does not have the sufficient rights if security is enabled fixes elastic#51728
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Jan 31, 2020
… enabled (elastic#51732) do index refresh of the internal transform index with the system user instead of using the calling user which does not have sufficient rights if security is enabled fixes elastic#51728
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Jan 31, 2020
… enabled (elastic#51732) do index refresh of the internal transform index with the system user instead of using the calling user which does not have sufficient rights if security is enabled fixes elastic#51728
This was referenced Jan 31, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
found via CI: #51629
If security is used and the transform user is a non-admin user
_transform/_stats
might return old state information after stopping the transform withwait_for_completion=true
. The information is correct eventually after the index is internally refreshed viarefresh_interval
(1s) of the underlying lucene index.Severity: Low, the problem only affects users(security enabled) that script transforms and rely on correct stats information.
Mitigation: Call
_stats
again if the expected output is wrong until the refresh has happened.The text was updated successfully, but these errors were encountered: