[
https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey E Rodriguez updated HDFS-11502:
----------------------------------------
Summary: dn.js set datanode UI to window.location.hostname, it should use
jmx bean property to setup hostname (was: dn.js set datanode UI to
window.location.hostname, it should use jmx
"qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get
tag.hostname)
> dn.js set datanode UI to window.location.hostname, it should use jmx bean
> property to setup hostname
> ----------------------------------------------------------------------------------------------------
>
> Key: HDFS-11502
> URL: https://issues.apache.org/jira/browse/HDFS-11502
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 2.7.2, 2.7.3
> Environment: all
> Reporter: Jeffrey E Rodriguez
> Assignee: Jeffrey E Rodriguez
> Fix For: 2.8.0, 2.7.3, 3.0.0-alpha1, 3.0.0-alpha2
>
> Attachments: HDFS-11502.001.patch
>
>
> Datanode UI calls dn.js which loads properties for datanode..
> dn.js sets datanode UI to window.location.hostname, it should use jmx
> "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get
> tag.hostname.
> The issue is that if we proxy datanode UI we would get the proxy as the
> hostname because UI code uses window.location.hostname instead of the actual
> datanode hostname.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
