[
https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HADOOP-3103:
--------------------------------------------
Attachment: HADOOP-3103.1.for.17
HADOOP-3103.1.for.16
Pch.. Stupid mistake. Reattaching both patches again.
> [HOD] Hadoop.tmp.dir should not be set to cluster directory
> -----------------------------------------------------------
>
> Key: HADOOP-3103
> URL: https://issues.apache.org/jira/browse/HADOOP-3103
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hod
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
> Fix For: 0.16.2
>
> Attachments: HADOOP-3103, HADOOP-3103.1.for.16, HADOOP-3103.1.for.17,
> HADOOP-3103.for.16, HADOOP-3103.for.17
>
>
> Currently HOD generates hadoop.tmp.dir pointing to the cluster
> directory(hod.clusterdir), which users typically create in their home
> directories. This hadoop.tmp.dir is used on the client side when a jar is
> run(org/apache/hadoop/util/RunJar.java). The user home directories might be
> NFS mounted in some environments, which might result in a hit, for example
> when running a jar.
> So, HOD *should not* generate hadoop.tmp.dir pointing to cluster directory.
> Instead, it should use hod.temp-dir, which *is* the location that
> dfs.client.buffer.dir uses to alleviate any such NFS hit problems. Further,
> though currently hadoop.tmp.dir is not used on hadoop daemons side, it would
> be good if HOD generates it on daemons side too, and thus preclude any
> related problems in future.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
