hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5217) DistCp fails when launched by Oozie in a secure cluster
Date Wed, 08 May 2013 19:27:16 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652250#comment-13652250
] 

Hadoop QA commented on MAPREDUCE-5217:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12582343/MAPREDUCE-5217-trunk.patch.2
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-tools/hadoop-distcp.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3596//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3596//console

This message is automatically generated.
                
> 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-trunk.patch, MAPREDUCE-5217-trunk.patch,
MAPREDUCE-5217-trunk.patch.2
>
>
> 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

Mime
View raw message