[
https://issues.apache.org/jira/browse/HDFS-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Marion updated HDFS-6307:
------------------------------
Description:
If you create a configuration based off of the example at [1], but you use the
nameservice MyCluster instead of mycluster, the Client will throw an
UnknownHostException if you try to use hdfs://mycluster. This works in a non-HA
configuration.
[1]
http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html
was:
If you create a configuration based off of the example at [1], but you use the
nameservice MyCluster instead of mycluster, the Client will throw an
UnknownHostException if you try to use hdfs://mycluster. I believe this works
in a non-HA configuration.
[1]
http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html
> Case Sensitivity issue with Client and HA configuration
> -------------------------------------------------------
>
> Key: HDFS-6307
> URL: https://issues.apache.org/jira/browse/HDFS-6307
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.4.0
> Environment: Hadoop 2.4.0
> HA NN Configuration
> Reporter: Dave Marion
>
> If you create a configuration based off of the example at [1], but you use
> the nameservice MyCluster instead of mycluster, the Client will throw an
> UnknownHostException if you try to use hdfs://mycluster. This works in a
> non-HA configuration.
> [1]
> http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
