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

Posted to issues@spark.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2014/09/03 21:11:51 UTC

[jira] [Commented] (SPARK-3375) spark on yarn alpha container allocation issues

    [ https://issues.apache.org/jira/browse/SPARK-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120281#comment-14120281 ] 

Thomas Graves commented on SPARK-3375:
--------------------------------------

It appears there is a race condition in which if you ask for the containers to soon yarn won't pick them up.  If I remove the call to     allocator.allocateResources() in the registerAM and let it wait until the report thread asks then it works.  I need to investigate more on the YARN side.


> spark on yarn alpha container allocation issues
> -----------------------------------------------
>
>                 Key: SPARK-3375
>                 URL: https://issues.apache.org/jira/browse/SPARK-3375
>             Project: Spark
>          Issue Type: Bug
>          Components: YARN
>    Affects Versions: 1.2.0
>            Reporter: Thomas Graves
>            Priority: Blocker
>
> It looks like if yarn doesn't get the containers immediately it stops asking for them and the yarn application hangs with never getting any executors.  This was introduced by https://github.com/apache/spark/pull/2169



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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