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

Posted to issues@tez.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2014/03/03 22:18:21 UTC

[jira] [Commented] (TEZ-708) Avoid asking for new containers in uber-local mode

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

Jonathan Eagles commented on TEZ-708:
-------------------------------------

[~sseth], [~bikassaha], [~airbots] Do have an idea for implementation of this? I can see this being implemented as LocalTaskScheduler or perhaps LocalTezAMRMClientAsync where requests for all containers return (possibly faked out) local containers up to a configurable maximum without need for communication to RM. The assumption here is that there is no TezMiniCluster running based on Tez Local Mode design (TEZ-684).

> Avoid asking for new containers in uber-local mode
> --------------------------------------------------
>
>                 Key: TEZ-708
>                 URL: https://issues.apache.org/jira/browse/TEZ-708
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Chen He
>            Assignee: Jonathan Eagles
>
> Once we finish this task, the TaskSchedulerEventHandler should not ask for new container in the Uber-mode.



--
This message was sent by Atlassian JIRA
(v6.2#6252)