[
https://issues.apache.org/jira/browse/HDFS-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368067#comment-14368067
]
Konstantin Shvachko edited comment on HDFS-7956 at 3/24/15 1:22 AM:
--------------------------------------------------------------------
Otherwise it is hard to identify DNs when they register, send reports or
heartbeats. Because the main DN port is not printed anywhere in
DatanodeRegistration.
Current:
{code}DatanodeRegistration(127.0.0.1,
datanodeUuid=532f1c1f-fe09-4ad4-8d7d-c58f7b8b32b0, infoPort=35614 ...){code}
Desired:
{code}DatanodeRegistration(127.0.0.1:46044,
datanodeUuid=532f1c1f-fe09-4ad4-8d7d-c58f7b8b32b0, infoPort=35614 ...){code}
The fix is to simply print {{DatanodeID}} via {{super.toString()}} instead of
{{getIpAddr()}}
was (Author: shv):
Otherwise it is hard to identify DNs when they register, send reports or
heartbeats. Because the main DN port is not printed anywhere in
DatanodeRegistration.
Current:
{code}DatanodeRegistration(127.0.0.1,
datanodeUuid=532f1c1f-fe09-4ad4-8d7d-c58f7b8b32b0, infoPort=35614 ...){code}
Desired:
{code}DatanodeRegistration(127.0.0.1:46044,
datanodeUuid=532f1c1f-fe09-4ad4-8d7d-c58f7b8b32b0, infoPort=35614 ...){code}
The fix is to simply print {{DatanodeID}} via {{super.toString()}} instead of
{{super.toString()}}
> Improve logging for DatanodeRegistration.
> -----------------------------------------
>
> Key: HDFS-7956
> URL: https://issues.apache.org/jira/browse/HDFS-7956
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.6.0
> Reporter: Konstantin Shvachko
> Assignee: Plamen Jeliazkov
> Attachments: HDFS-7956.1.patch
>
>
> {{DatanodeRegistration.toString()}}
> prints only its address without the port, it should print its full address,
> similar {{NamenodeRegistration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
