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

[ML] DF Analytics times out after 30 minutes #45723

Closed
dimitris-athanasiou opened this issue Aug 20, 2019 · 1 comment · Fixed by #45724
Closed

[ML] DF Analytics times out after 30 minutes #45723

dimitris-athanasiou opened this issue Aug 20, 2019 · 1 comment · Fixed by #45724
Assignees
Labels
>bug :ml Machine learning

Comments

@dimitris-athanasiou
Copy link
Contributor

dimitris-athanasiou commented Aug 20, 2019

If the analytics process takes more than 30 minutes to complete, the task is timing out.

The logs show this with:

[2019-08-14T00:03:27,523][WARN ][o.e.x.m.d.p.AnalyticsResultProcessor] [reba.attlocal.net] [allstate-train] Timeout waiting for results processor to complete
[2019-08-14T00:03:27,527][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [reba.attlocal.net] [allstate-train] Result processor has completed
[2019-08-14T00:03:27,527][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [reba.attlocal.net] [allstate-train] Closing process
[2019-08-14T00:03:32,534][WARN ][o.e.x.m.p.AbstractNativeProcess] [reba.attlocal.net] [allstate-train] Exception closing the running analytics process
java.util.concurrent.TimeoutException: null
    at java.util.concurrent.FutureTask.get(FutureTask.java:204) ~[?:?]
    at org.elasticsearch.xpack.ml.process.AbstractNativeProcess.close(AbstractNativeProcess.java:163) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
    at org.elasticsearch.xpack.ml.dataframe.process.AnalyticsProcessManager.closeProcess(AnalyticsProcessManager.java:195) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
    at org.elasticsearch.xpack.ml.dataframe.process.AnalyticsProcessManager.processData(AnalyticsProcessManager.java:104) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
    at org.elasticsearch.xpack.ml.dataframe.process.AnalyticsProcessManager.lambda$runJob$1(AnalyticsProcessManager.java:69) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
    at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:699) [elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
    at java.lang.Thread.run(Thread.java:835) [?:?]
[2019-08-14T00:03:32,550][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [reba.attlocal.net] [allstate-train] Closed process
[2019-08-14T00:03:32,550][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [reba.attlocal.net] [allstate-train] Marking task completed

The reason is a misplaced timeout in the results processor.

@dimitris-athanasiou dimitris-athanasiou changed the title [ML [ML] DF Analytics times out after 30 minutes Aug 20, 2019
@dimitris-athanasiou dimitris-athanasiou self-assigned this Aug 20, 2019
@dimitris-athanasiou dimitris-athanasiou added :ml Machine learning >bug labels Aug 20, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core

dimitris-athanasiou added a commit to dimitris-athanasiou/elasticsearch that referenced this issue Aug 20, 2019
…omplete

We cannot know how long the analysis will take to complete thus we should not have
a timeout. Note that if the process crashes, the result processor will pick the
exception due to the stream closing.

Closes elastic#45723
dimitris-athanasiou added a commit that referenced this issue Aug 20, 2019
…omplete (#45724)

We cannot know how long the analysis will take to complete thus we should not have
a timeout. Note that if the process crashes, the result processor will pick the
exception due to the stream closing.

Closes #45723
dimitris-athanasiou added a commit to dimitris-athanasiou/elasticsearch that referenced this issue Aug 20, 2019
… to complete (elastic#45724)

We cannot know how long the analysis will take to complete thus we should not have
a timeout. Note that if the process crashes, the result processor will pick the
exception due to the stream closing.

Closes elastic#45723
dimitris-athanasiou added a commit that referenced this issue Aug 20, 2019
… to complete (#45724) (#45733)

We cannot know how long the analysis will take to complete thus we should not have
a timeout. Note that if the process crashes, the result processor will pick the
exception due to the stream closing.

Closes #45723
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :ml Machine learning
Projects
None yet
2 participants