[
https://issues.apache.org/jira/browse/HDFS-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560746#comment-14560746
]
Vinayakumar B commented on HDFS-7161:
-------------------------------------
After HDFS-7579, no longer hashcode printed for any DataNode commands. Instead
it prints the short classname with action(command id). like below:
{noformat} Got back one command: FinalizeCommand/5.{noformat}
However, the proposed patch was only covering FinalizeCommand, but HDFS-7579
covered all subclasses of {{ServerCommand}}.
And related to same exception message, Its Okay to have same exception message,
as the difference can be found out, in the message itself.
{{id.toString()}} and {{block}}, will include both blockpoolId and blockId. So
there is no need to explain again in the message.
So resolving this as duplicate, Feel free to re-open if required.
> Hashcode is logging while logging block report message
> ------------------------------------------------------
>
> Key: HDFS-7161
> URL: https://issues.apache.org/jira/browse/HDFS-7161
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.7.0
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Priority: Minor
> Labels: BB2015-05-TBR
> Attachments: HDFS-7161-002.patch, HDFS-7161.patch, Hadoop-8252.patch
>
>
> Scenario:
> =========
> Start NN and DN.
> Check log messgae in DN..It's coming like following
> 2012-03-13 14:34:36,008 INFO org.apache.hadoop.hdfs.server.datanode.DataNode:
> sent block report, processed
> command:org.apache.hadoop.hdfs.server.protocol.FinalizeCommand@43deff3
> line num 413 in BpserviceActor.java LOG.info("sent block report, processed
> command:" + cmd);
> line num 388 in BpserviceActor.java cmd =
> bpNamenode.blockReport(bpRegistration,bpos.getBlockPoolId(), report);
> It's better log message instead of hashcode
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
