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

ASF GitHub Bot logged work on HDFS-16584:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/May/22 14:06
            Start Date: 22/May/22 14:06
    Worklog Time Spent: 10m 
      Work Description: Hexiaoqiao commented on PR #4333:
URL: https://github.com/apache/hadoop/pull/4333#issuecomment-1133903390

   @jianghuazhu Thanks for your contribution. It could not cherry-pick to 
branch-3.3 smoothly. Would you mind have another check or submit another PR for 
branch-3.3 if need. Thanks.




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

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

> Record StandbyNameNode information when Balancer is running
> -----------------------------------------------------------
>
>                 Key: HDFS-16584
>                 URL: https://issues.apache.org/jira/browse/HDFS-16584
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: balancer & mover, namenode
>    Affects Versions: 3.3.0
>            Reporter: JiangHua Zhu
>            Assignee: JiangHua Zhu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>         Attachments: image-2022-05-19-20-23-23-825.png
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When the Balancer is running, we allow block data to be fetched from the 
> StandbyNameNode, which is nice. Here are some logs:
>  !image-2022-05-19-20-23-23-825.png! 
> But we have no way of knowing which NameNode the request was made to. We 
> should log more detailed information, such as the host associated with the 
> StandbyNameNode.



--
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