[
https://issues.apache.org/jira/browse/HADOOP-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248544#comment-13248544
]
Suresh Srinivas commented on HADOOP-8252:
-----------------------------------------
Other logs that should be fixed:
Log message is same for two different conditions in
BlockTokenSecretManager#checkAccess()
{noformat}
if (!id.getBlockPoolId().equals(block.getBlockPoolId())) {
throw new InvalidToken("Block token with " + id.toString()
+ " doesn't apply to block " + block);
}
if (id.getBlockId() != block.getBlockId()) {
throw new InvalidToken("Block token with " + id.toString()
+ " doesn't apply to block " + block);
}
{noformat}
> Hashcode is logging while logging block report message
> ------------------------------------------------------
>
> Key: HADOOP-8252
> URL: https://issues.apache.org/jira/browse/HADOOP-8252
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 2.0.0
> Reporter: Brahma Reddy Battula
> Priority: Trivial
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
