[
https://issues.apache.org/jira/browse/HDFS-10735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412755#comment-15412755
]
Hadoop QA commented on HDFS-10735:
----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color}
| {color:red} HDFS-10735 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12822708/HDFS-10735-001.patch |
| JIRA Issue | HDFS-10735 |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/16349/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> Distcp using webhdfs on secure HA clusters fails with StandbyException
> ----------------------------------------------------------------------
>
> Key: HDFS-10735
> URL: https://issues.apache.org/jira/browse/HDFS-10735
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 2.7.2
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Fix For: 2.8.0
>
> Attachments: HDFS-10735-001.patch, exception.txt
>
>
> A distcp running on HADOOP 2.7.2 cluster , copying from HADOOP 2.4.1 cluster
> fails.
> Both are secure clusters.
> The logs indicates that task contacts the StandBy name node on the remote
> cluster is contacted first and gets a standByException.
> Instead of retrying with the active name node on the remote cluster, the
> execution errors out throwing InvalidToken
> The exception is attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
