[ https://issues.apache.org/jira/browse/MAPREDUCE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090684#comment-14090684 ]
Hudson commented on MAPREDUCE-6021: ----------------------------------- FAILURE: Integrated in Hadoop-Yarn-trunk #638 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/638/]) MAPREDUCE-6021. MR AM should have working directory in LD_LIBRARY_PATH. Contributed by Jason Lowe (jlowe: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1616585) * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/YARNRunner.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/TestYARNRunner.java > MR AM should have working directory in LD_LIBRARY_PATH > ------------------------------------------------------ > > Key: MAPREDUCE-6021 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6021 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mr-am > Affects Versions: 2.4.1 > Reporter: Jason Lowe > Assignee: Jason Lowe > Fix For: 3.0.0, 2.6.0 > > Attachments: MAPREDUCE-6021-v2.patch, MAPREDUCE-6021.patch > > > Tasks implicitly pick up shared libraries added to the job because the task > launch context explicitly adds the container working directory to > LD_LIBRARY_PATH. However the same is not done for the AM container which is > inconsistent. User code can run in the AM via output committer, speculator, > uber job, etc., so the AM's LD_LIBRARY_PATH should have the container work > directory for consistency with tasks. -- This message was sent by Atlassian JIRA (v6.2#6252)