[
https://issues.apache.org/jira/browse/TEZ-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090671#comment-14090671
]
Chen He commented on TEZ-1393:
------------------------------
I agree that we need to change "TezUtils.addUserSpecifiedTezConfiguration". As
well as the staging dir. Because if there are concurrent DAGs running in local
mode, it will be problematic since each DAG may create a pb file.
My question is if we hard code the working-directory to be ".", we add
dependency to the user current environment. I mean what if user has background
programs that changing contents under "."? I think, TEZ-1337 can help, I mean
we read from configuration. Also the configuration is useful for us to reduce
dependency on node manager configuration(nm-local.dir) for shuffle.
some minor issues:
In DAGAppMapster first constructor (top to down), variable "clock" is never
used; line 1468, "recoveredDAGData" is not necessary to be created; other
warnings in related java file.
> user.dir should not be reset in LocalMode
> -----------------------------------------
>
> Key: TEZ-1393
> URL: https://issues.apache.org/jira/browse/TEZ-1393
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Priority: Critical
> Attachments: TEZ-1393.1.txt
>
>
> Setting user.dir to the staging-dir has the implication of changing the root
> of the filesystem to the staging directory, which is application specific.
> If using multiple instance of LocalClient within a single JVM - this can get
> problematic, between multiple jobs since the CWD will change in the middle of
> execution - which ends up disallowing usage of relative paths.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
