[ 
https://issues.apache.org/jira/browse/HADOOP-19683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sunhui updated HADOOP-19683:
----------------------------
    Environment: !image-2025-09-10-10-12-28-486.png|width=417,height=228!  
(was: !image-2025-09-10-10-12-28-486.png!)

> HDFS NameNode Web UI generates invalid HTTP links for DataNodes in IPv6 
> environment
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-19683
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19683
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 3.4.1
>         Environment: !image-2025-09-10-10-12-28-486.png|width=417,height=228!
>            Reporter: sunhui
>            Priority: Minor
>         Attachments: image-2025-09-10-10-12-28-486.png
>
>
> In the HDFS NameNode Web UI 
> (http://nn-host:9870/dfshealth.html#tab-datanode), the "Http Address" column 
> for DataNodes generates completely corrupt and invalid links when the 
> DataNode's address is an IPv6 literal.
> 1. It fails to encapsulate the IPv6 address in square brackets `[]`, which is 
> required by RFC 2732. 2. More critically, it appears to **parse the IPv6 
> address incorrectly**, mistaking a part of the address (e.g., the `30` in 
> `1172:30:...`) for the port number, which completely breaks the URL. This 
> results in a malformed, unclickable link that does not point to the 
> DataNode's web interface. **Current Behavior & Evidence:** The DataNode's 
> actual address is: `[1172:30:0:0:0:0:8a34]:50010` However, the NameNode UI 
> displays the link as: `https://datanodeHostname:30` This link is **invalid** 
> and leads nowhere. The UI has: - Stripped the original port `50010`. - 
> Incorrectly extracted `30` (which is part of the IPv6 address) and used it as 
> the port. - Failed to wrap the IPv6 address, leading to incorrect parsing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to