[
https://issues.apache.org/jira/browse/SPARK-14953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332560#comment-15332560
]
Cheng Lian commented on SPARK-14953:
Marked this as won't fix since this isn't causing any actual problems right
now. We hit this issue because there was a locality bug in an intermediate
version of [PR #12527|https://github.com/apache/spark/pull/12527]. See
[here|https://github.com/apache/spark/pull/12527#issuecomment-213034425].
> LocalBackend should revive offers periodically
> --
>
> Key: SPARK-14953
> URL: https://issues.apache.org/jira/browse/SPARK-14953
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
>Affects Versions: 2.0.0
>Reporter: Cheng Lian
>
> {{LocalBackend}} only revives offers when tasks are submitted, succeed, or
> fail. This may lead to deadlock due to delayed scheduling. A case study is
> provided in [this PR
> comment|https://github.com/apache/spark/pull/12527#issuecomment-213034425].
> Basically, a job may have a task is delayed to be scheduled due to locality
> mismatch. The default delay timeout is 3s. If all other tasks finish during
> this period, {{LocalBackend}} won't revive any offer after the timeout since
> no tasks are submitted, succeed or fail then. Thus, the delayed task will
> never be scheduled again and the job never completes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
