[
https://issues.apache.org/jira/browse/HDFS-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993049#comment-13993049
]
Kihwal Lee commented on HDFS-6329:
----------------------------------
Ouch. Now you know what I use as a debug marker in logs. I will take it out.
bq. Maybe I missed it, but a test cast to simulate our HA IP-failover would be
invaluable to preventing another regression.
That's very tricky with the current state of MiniDFSCluster and other broken
checks in HA. HDFS-6360 will fix MiniDFSCluster and HDFS-6334 will fix HA
checks. Perhap we can add more meaningful tests after that.
> WebHdfs does not work if HA is enabled on NN but logical URI is not
> configured.
> -------------------------------------------------------------------------------
>
> Key: HDFS-6329
> URL: https://issues.apache.org/jira/browse/HDFS-6329
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Blocker
> Fix For: 3.0.0, 2.4.1
>
> Attachments: HDFS-6329.patch, HDFS-6329.patch, HDFS-6329.v2.patch,
> HDFS-6329.v3.patch, HDFS-6329.v4.patch, HDFS-6329.v5.patch
>
>
> After HDFS-6100, namenode unconditionally puts the logical name (name service
> id) as the token service when redirecting webhdfs requests to datanodes, if
> it detects HA.
> For HA configurations with no client-side failover proxy provider (e.g. IP
> failover), webhdfs does not work since the clients do not use logical name.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
