You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Imran Rashid (JIRA)" <ji...@apache.org> on 2017/05/23 16:21:04 UTC
[jira] [Commented] (SPARK-4921) TaskSetManager mistakenly returns
PROCESS_LOCAL for NO_PREF tasks
[ https://issues.apache.org/jira/browse/SPARK-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021410#comment-16021410 ]
Imran Rashid commented on SPARK-4921:
-------------------------------------
I want to point out that this also results in really confusing behavior in the event logs and the UI -- no pref tasks show up as "Process local" in the UI. This doesn't adversely effect scheduling, but is very confusing for the user.
I know this is really old, but just curious [~CodingCat] if you remember why this was done in SPARK-2294.
> TaskSetManager mistakenly returns PROCESS_LOCAL for NO_PREF tasks
> -----------------------------------------------------------------
>
> Key: SPARK-4921
> URL: https://issues.apache.org/jira/browse/SPARK-4921
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.2.0
> Reporter: Xuefu Zhang
> Attachments: NO_PREF.patch
>
>
> During research for HIVE-9153, we found that TaskSetManager returns PROCESS_LOCAL for NO_PREF tasks, which may caused performance degradation. Changing the return value to NO_PREF, as demonstrated in the attached patch, seemingly improves the performance.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org