[
https://issues.apache.org/jira/browse/HDFS-11691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983855#comment-15983855
]
Hudson commented on HDFS-11691:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11628 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11628/])
HDFS-11691. Add a proper scheme to the datanode links in NN web UI. (jlowe: rev
e4321ec84321672a714419278946fe1012daac71)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfshealth.html
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfshealth.js
> Add a proper scheme to the datanode links in NN web UI
> ------------------------------------------------------
>
> Key: HDFS-11691
> URL: https://issues.apache.org/jira/browse/HDFS-11691
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Fix For: 2.9.0, 3.0.0-alpha3, 2.8.1
>
> Attachments: HDFS-11691.patch
>
>
> On the datanodes page of the namenode web UI, the datanode links may not be
> correct if the namenode is serving the page through http but https is also
> enabled. This is because {{dfshealth.js}} does not put a proper scheme in
> front of the address. It already determines whether the address is
> non-secure or secure. It can simply prepend {{http:}} or {{https:}} to what
> it is currently setting.
> The existing mechanism would work for YARN and MAPRED, since they can only
> serve one protocol, HTTP or HTTPS.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
