hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3236) Distcp with hdfs:// passed with error in JT log while copying from .20.204 to .20.205 ( with useIp=false)
Date Thu, 20 Oct 2011 19:34:10 GMT

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

Hadoop QA commented on MAPREDUCE-3236:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12499756/HDFS-2447-1.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1086//console

This message is automatically generated.
                
> Distcp with hdfs:// passed with error in JT log while copying from .20.204  to .20.205
( with useIp=false)
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3236
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3236
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker, security
>    Affects Versions: 0.20.205.0
>            Reporter: Rajit Saha
>            Assignee: Daryn Sharp
>         Attachments: HDFS-2447-1.patch, HDFS-2447.patch
>
>
> I tried to copy file from .20.204 to .20.205 by distcp over hdfs:// while using hadoop.security.token.service.use_ip=false
in core-site.xml. The copy was successful but found error " org.apache.hadoop.mapreduce.security.token.DelegationTokenRenewal:"
exception in .20.205 JT.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message