[ 
https://issues.apache.org/jira/browse/HADOOP-18209?focusedWorklogId=765528&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-765528
 ]

ASF GitHub Bot logged work on HADOOP-18209:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/May/22 16:38
            Start Date: 03/May/22 16:38
    Worklog Time Spent: 10m 
      Work Description: prasad-acit commented on PR #4184:
URL: https://github.com/apache/hadoop/pull/4184#issuecomment-1116306155

   > Thank you @liuml07 , 
[HADOOP-17800](https://issues.apache.org/jira/browse/HADOOP-17800) got branched 
out from trunk recently & started merging from older IPv6 branch 
([HADOOP-11890](https://issues.apache.org/jira/browse/HADOOP-11890)). Yes, 
@brahmareddybattula can clarify it further.
   
   @hemanthboyina Do you have any thought on this?




Issue Time Tracking
-------------------

    Worklog Id:     (was: 765528)
    Time Spent: 1h 20m  (was: 1h 10m)

> Fix links to DataNodes in NameNode UI to support IPv6
> -----------------------------------------------------
>
>                 Key: HADOOP-18209
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18209
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Renukaprasad C
>            Assignee: Renukaprasad C
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: image-2022-04-17-08-39-20-926.png, 
> image-2022-04-18-21-52-46-661.png
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> IPv6 second group getting displayed as port number and which lead to error in 
> opening the DN webpage from NN Web UI.
>  
> !image-2022-04-17-08-39-20-926.png!
>  
> After fix: IPv6 Address & Port parsed correctly & link open the DN webpage 
> normally.
> !image-2022-04-18-21-52-46-661.png!



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Reply via email to