[
https://issues.apache.org/jira/browse/HDFS-16584?focusedWorklogId=772737&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-772737
]
ASF GitHub Bot logged work on HDFS-16584:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 20/May/22 09:27
Start Date: 20/May/22 09:27
Worklog Time Spent: 10m
Work Description: jianghuazhu commented on PR #4333:
URL: https://github.com/apache/hadoop/pull/4333#issuecomment-1132683576
@ayushtkn @Hexiaoqiao , can you guys help to review this pr.
Thank you very much.
Issue Time Tracking
-------------------
Worklog Id: (was: 772737)
Time Spent: 40m (was: 0.5h)
> 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
> Attachments: image-2022-05-19-20-23-23-825.png
>
> Time Spent: 40m
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
