[
https://issues.apache.org/jira/browse/HDFS-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Saxena resolved HDFS-16290.
---------------------------------
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
Committed to trunk.
Thanx [~jianghuazhu] for the contribution!!!
> Make log more standardized when executing verifyAndSetNamespaceInfo()
> ---------------------------------------------------------------------
>
> Key: HDFS-16290
> URL: https://issues.apache.org/jira/browse/HDFS-16290
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Affects Versions: 2.9.2
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Attachments: screenshot-1.png
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> When verifyAndSetNamespaceInfo() is executed, the log will record some
> information. E.g:
> '
> 2021-10-27 18:08:36,242 [50867]-INFO
> [Thread-33:BPOfferService@376]-Acknowledging ACTIVE Namenode during
> handshakeBlock pool BP-597961518-xxx.xxx.xxx.xxx-1534758275943 (Datanode Uuid
> 9b2aedc9-f8b2 -4ee2-b99f-877bc6e42c87) service to
> xxxx.xxx.xxx.org/xxxx.xxx.xxx.xxx:8021
> '
> Here, the connection between the'handshake' and the'Block pool' is too tight,
> and the readability is not good.
> !screenshot-1.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
