You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2019/02/12 21:32:00 UTC

[jira] [Resolved] (SPARK-19894) Tasks entirely assigned to one executor on Yarn-cluster mode for default-rack

     [ https://issues.apache.org/jira/browse/SPARK-19894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcelo Vanzin resolved SPARK-19894.
------------------------------------
    Resolution: Won't Fix

See discussion in PR. My reading is that it was decided this was an env problem, not a Spark problem.

> Tasks entirely assigned to one executor on Yarn-cluster mode for default-rack
> -----------------------------------------------------------------------------
>
>                 Key: SPARK-19894
>                 URL: https://issues.apache.org/jira/browse/SPARK-19894
>             Project: Spark
>          Issue Type: Bug
>          Components: Scheduler, YARN
>    Affects Versions: 2.1.0
>         Environment: Yarn-cluster
>            Reporter: Yuechen Chen
>            Priority: Major
>
> In YARN-cluster mode, if driver has no rack information on two different hosts, these two hosts would both be recoginized as "/default-rack", which may cause some bugs.
> For example, if hosts of one executor and one external datasource are unknown by driver, this two hosts would be recoginized as the same rack "/default-rack", and then all tasks would be assigned to the executor.
> This bug would be avoided, if getRackForHost("unknown host") in YarnScheduler returns None, not Some("/default-rack").



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org