[
https://issues.apache.org/jira/browse/TEZ-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180359#comment-15180359
]
Hitesh Shah commented on TEZ-1210:
----------------------------------
You can submit the dag plan via rpc in non-session mode too but from a
performance view point it is likely to be a bit slower. The client would need
to submit the app, wait for the AM to come up and then submit the DAG. For
non-session mode, it is simpler to use local resources as the dag is available
to be executed as soon as the AM comes up as it is available in its local
container dir. There are other fault tolerance scenario questions too - what if
the first AM attempt crashes before the dag could be submitted to it or if the
cluster is busy and the AM does not come up for quite some time - this would
require the client process to remain around for a long time to submit the dag
over rpc. Using local resource in this case allows the client to be a fire and
forget which is useful for ETL scripts that submit only one DAG.
> TezClientUtils.localizeDagPlanAsText() needs to be fixed for session mode
> -------------------------------------------------------------------------
>
> Key: TEZ-1210
> URL: https://issues.apache.org/jira/browse/TEZ-1210
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Assignee: Alexander Pivovarov
> Labels: newbie
> Fix For: 0.5.2
>
> Attachments: TEZ-1210.1.patch, TEZ-1210.2.patch
>
>
> It writes the dagPlan in text form to the same location. Either it should not
> be invoked in session mode or it should written with a differentiating prefix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
