[ https://issues.apache.org/jira/browse/MAPREDUCE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652545#comment-13652545 ]
Venkat Ranganathan commented on MAPREDUCE-5217: ----------------------------------------------- Thanks [~sseth]. I have updated the trunk patch as you suggested and also changed the variable name to tokenFile as suggested by [~jnp]. I am uploading the trunk patch first and will upload the branch-1 patch with new variable name after precommit tests with trunk patch are done > DistCp fails when launched by Oozie in a secure cluster > ------------------------------------------------------- > > Key: MAPREDUCE-5217 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5217 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: distcp, security > Affects Versions: trunk, 1.1.2, 2.0.4-alpha > Environment: Hadoop secure cluster > Reporter: Venkat Ranganathan > Assignee: Venkat Ranganathan > Attachments: MAPREDUCE-5217-branch-1.patch, > MAPREDUCE-5217-branch-1.patch.2, MAPREDUCE-5217-trunk.patch, > MAPREDUCE-5217-trunk.patch, MAPREDUCE-5217-trunk.patch.2, > MAPREDUCE-5217-trunk.patch.3 > > > As mentioned in MAPREDUCE-4324, Oozie has the following boilerplate code in > in the main launcher for Pig, Hive, MR and Sqoop actions. > if (System.getenv("HADOOP_TOKEN_FILE_LOCATION") != null) { > jobConf.set("mapreduce.job.credentials.binary", > System.getenv("HADOOP_TOKEN_FILE_LOCATION")); > } > For Java action, which does not have a main launcher in oozie, the above > codecan be added by the user as the user purportedly has the code that is > launched. > But for DistCp action, the user has no such luxury. The solution attempted in > MAPREDUCE-4324 would have helped DistCp, but it was not implemented as it > would break MAPREDUCE-3727. So, we have to fix DistCp and > add the same boilerplate code so that DistCp action can be launched by Oozie > in a secure cluster. > The code added checks for an System env. variable to be set which is not > typically set in normal command line execution of DistCp, DistCp runs fine > with commnad line usage both in secure and non-secure cluster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira