You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2008/03/27 06:49:29 UTC
[jira] Created: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
[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
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.
[jira] Updated: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated HADOOP-3103:
--------------------------------------------
Affects Version/s: 0.16.0
> [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
> Affects Versions: 0.16.0
> 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.
[jira] Commented: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Amir Youssefi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582528#action_12582528 ]
Amir Youssefi commented on HADOOP-3103:
---------------------------------------
Thanks for confirming the requested priority. Please let me know if you need more details.
+1 for making the change.
> [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
>
>
> 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.
[jira] Commented: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582900#action_12582900 ]
Vinod Kumar Vavilapalli commented on HADOOP-3103:
-------------------------------------------------
Console output shows that javadoc warnings are related to src/java/org/apache/hadoop/net/SocketInputStream.java:137 and src/java/org/apache/hadoop/net/SocketOutputStream.java:132. There appear to be two javadoc warnings thus, but the final results report only one (??).
In any case, the warnings are not pertinent to this patch. Patch is committable.
> [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
> Affects Versions: 0.16.0
> 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.
[jira] Commented: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582585#action_12582585 ]
Hemanth Yamijala commented on HADOOP-3103:
------------------------------------------
This patch for 16 seems to be not against the branch. Can you pl. regenerate.
> [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.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.
[jira] Commented: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582744#action_12582744 ]
Hadoop QA commented on HADOOP-3103:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12378704/HADOOP-3103.1.for.17
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included +1. The patch appears to include 3 new or modified tests.
javadoc -1. The javadoc tool appears to have generated 1 warning messages.
javac +1. The applied patch does not generate any new javac compiler warnings.
release audit +1. The applied patch does not generate any new release audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2078/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2078/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2078/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2078/console
This message is automatically generated.
> [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.
[jira] Commented: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582655#action_12582655 ]
Hemanth Yamijala commented on HADOOP-3103:
------------------------------------------
+1 for the patch. Validated against both 16 branch and trunk. Verified the hadoop.tmp.dir value is set to the hod.temp-dir and dfs.client.buffer.dir is set to hadoop.tmp.dir/dfs/tmp. Verified also that while running a job, the jar file is expanded in this directory, and it is cleaned up at the end.
> [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.
[jira] Updated: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-3103:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Vinod!
> [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
> Affects Versions: 0.16.0
> 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.
[jira] Updated: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ 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
Attaching a patch.
On client side, hadoop-tmp-dir is now created under hod.temp-dir/user.jobid/ and dfs.client.buffer.dir in hadoop-tmp-dir/dfs/tmp. On daemons side, hadoop-tmp-dir is created under work-dirs/...../hadoop-tmp, everything else remains unchanged.
> [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
>
>
> 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.
[jira] Commented: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583004#action_12583004 ]
Hudson commented on HADOOP-3103:
--------------------------------
Integrated in Hadoop-trunk #444 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/444/])
> [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
> Affects Versions: 0.16.0
> 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.
[jira] Updated: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ 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.for.17
HADOOP-3103.for.16
Attaching two patches: HADOOP-3103.for.16 and HADOOP-3103.for.17.
* The patch for Hadoop 17 has testcases, while the one for Hadoop 16 doesn't (and it cannot have, 'coz the testcase framework is not there in 16).
* testcases are written for verifying the presence of the parameter only on the client side. Testcases for server side are more involving. Skipping them for now, seems ok, 'coz, as of now, the parameter is not going to be used at all on the server side.
* As per Hemanth's comments(outside Jira), making hadoop.tmp.dir as a single value parameter instead of a comma separated list, which seems to be how hadoop.tmp.dir is being used currently.
* Hadoop.tmp.dir *is* marked final on daemons side, so client side config parameter won't override this on the server side.
> [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.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.
[jira] Updated: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
set to cluster directory
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated HADOOP-3103:
-------------------------------------
Status: Patch Available (was: Open)
Running through hudson.
> [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.