[
https://issues.apache.org/jira/browse/TEZ-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919713#comment-13919713
]
Bikas Saha commented on TEZ-708:
--------------------------------
I am not saying I am sure of it. Though I do feel that for the near to mid-term
we are not getting close to it. So for the purposes of local mode we should do
the simplest/cleanest thing that gets us to working on local mode for full
jobs. That will be an immense step forward for users as well as us to enable
faster testing and local debugger capability. Also, if we take the suggested
TaskSchedulerEventHandler approach then it does not seem like we are blocking
any future effort towards unifying the logic with mixed mode. So my suggestion
is to adopt the TaskSchedulerEventHandler (+LocalTaskScheduler) route and solve
this problem now. There are more complicated issues (like Shuffle eg) that are
need more attention right now.
> 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)
