You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/08/07 00:16:04 UTC

[jira] [Commented] (REEF-568) Work around the federated YARN container allocation problem

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

Markus Weimer commented on REEF-568:
------------------------------------

{quote}
We need to do a work around to the federated YARN container allocation issue. 
{quote}

Can you please be more specific on the issue we face?

> Work around the federated YARN container allocation problem
> -----------------------------------------------------------
>
>                 Key: REEF-568
>                 URL: https://issues.apache.org/jira/browse/REEF-568
>             Project: REEF
>          Issue Type: Task
>            Reporter: Ignacio Cano
>            Assignee: Ignacio Cano
>            Priority: Minor
>
> We need to do a work around to the federated YARN container allocation issue. 
> YARN client library calls the onError callback on YarnContainerManager with a Throwable. Either we can inspect the Throwable and identify what is the error (multiple allocations for one request) and ignore it silently, or we will have to "override" the class in the YARN client library that makes that call.
> As Markus suggested, we can guard our onError with a configuration parameter.



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