You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "David Sidlo (JIRA)" <ji...@apache.org> on 2016/08/17 22:24:20 UTC
[jira] [Updated] (HADOOP-13509) "fs -getmerge" can fail in an HA
NameNode env.
[ https://issues.apache.org/jira/browse/HADOOP-13509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Sidlo updated HADOOP-13509:
---------------------------------
Affects Version/s: (was: 2.7.0)
2.7.1
Environment: HDP 2.4.2, HA Cluster (was: HA Cluster, using "hdfs dfs =getmerge ..." or "hadoop fs -getmerge...")
Labels: HA dfs fs getmerge hadoop hdfs (was: )
> "fs -getmerge" can fail in an HA NameNode env.
> ----------------------------------------------
>
> Key: HADOOP-13509
> URL: https://issues.apache.org/jira/browse/HADOOP-13509
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.7.1
> Environment: HDP 2.4.2, HA Cluster
> Reporter: David Sidlo
> Priority: Minor
> Labels: HA, dfs, fs, getmerge, hadoop, hdfs
>
> In an HA cluster env with nn1 (standby) and nn2 (active), "hdfs dfs -getmerge" of "hadoop fs -getmerge" can fail. It references the wrong NameNode (nn1 standby), instead of nn2 (active).
> A work-around is to add "hdfs://<activeNameNodeHost>/", or "hdfs://<clusterName>/", to the start of the first parameter (source in hdfs).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org