-
Notifications
You must be signed in to change notification settings - Fork 62
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
[ML] Autodetect process crashes when trying to forecast on job upgraded from 6.2.4 to 6.3.1 #135
Comments
I found that if the job is created in 5.6.10 and then upgraded straight to 6.3.1, the job fails to open. ES log lines of the operation: 5610_job_in_631.log |
…detect process (elastic#136) Closes elastic#135.
The 5.6.10 upgrade is crashing in:
So In fact, This won't be fixed by #136. It requires a different fix. |
I think I'd prefer to address this under a separate issue. This affects a different upgrade path, i.e. jumping from 5.6 to 6.3. It will work ok upgrading to an intermediate state (so there exists a work around) also it is in a different area of the code. |
Found in
6.3.1
. Can be reproduced in6.3.0
.The issue can be reproduced by running a job using the
high_count
function on thedns_tunneling
dataset with a30m
bucket span.While running a
6.3.1
ES instance that was upgraded from version6.2.4
, if the user tries to forecast on thedns_tunneling
job that was created in version6.2.4
, the autodetect process will crash as soon as the forecast request is sent.ES logs show:
Steps to reproduce
6.2.4
ES instance and run a job using thehigh_count
function on thedns_tunneling
dataset with a30m
bucket span.6.3.1
dns_tunneling
job that was created in version6.2.4
failed
The text was updated successfully, but these errors were encountered: