[
https://issues.apache.org/jira/browse/SPARK-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553510#comment-14553510
]
Apache Spark commented on SPARK-7779:
-------------------------------------
User 'andrewor14' has created a pull request for this issue:
https://github.com/apache/spark/pull/6301
> Dynamic allocation: confusing message when canceling requests
> -------------------------------------------------------------
>
> Key: SPARK-7779
> URL: https://issues.apache.org/jira/browse/SPARK-7779
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.4.0
> Reporter: Andrew Or
> Assignee: Andrew Or
>
> Right now a long-running job with DA outputs the following. This is somewhat
> confusing to the user (why is my new desired total dropping??)
> {code}
> INFO ExecutorAllocationManager: Requesting 0 new executor(s) because tasks
> are backlogged (new desired total will be 46)
> INFO ExecutorAllocationManager: Requesting 0 new executor(s) because tasks
> are backlogged (new desired total will be 44)
> INFO ExecutorAllocationManager: Requesting 0 new executor(s) because tasks
> are backlogged (new desired total will be 42)
> INFO ExecutorAllocationManager: Requesting 0 new executor(s) because tasks
> are backlogged (new desired total will be 40)
> INFO ExecutorAllocationManager: Requesting 0 new executor(s) because tasks
> are backlogged (new desired total will be 38)
> INFO ExecutorAllocationManager: Requesting 0 new executor(s) because tasks
> are backlogged (new desired total will be 36)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
