[
https://issues.apache.org/jira/browse/TEZ-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919693#comment-13919693
]
Siddharth Seth commented on TEZ-708:
------------------------------------
Are you saying a decision to run within the AM / in a separate container will
always be taken by the DAG/Vertex - and the TaskScheduler never needs to make
this call ? Local containers can be considered as any other containers, and the
TaskScheduler becomes the one place which knows how to match resources,
locality requests, affinity etc.
bq. The TaskScheduler is already very complicated and in need of some
structural changes. My suggestion would be to avoid touching it for local mode
at this point. It will only make life hard for you without any
obvious/immediate benefit. Lets get full local mode up and running. Later, once
we figure out how to run mixed mode, we can revisit potential for merging logic.
I'd mentioned in my previous comment, we should be able to setup a
LocalTezAMRMClientAsync - without having to touch logic in the TaskScheduler -
and then at a later point, modify the TaskScheduler if required.
If we're sure that contianers running within the AM will never require any of
the logic in the TaskScheduler - then I agree with changing the
TaskSchedulerEventHandler, since that's a simpler change.
> 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)
