[
https://issues.apache.org/jira/browse/HDFS-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620043#comment-13620043
]
Aaron T. Myers commented on HDFS-4658:
--------------------------------------
Thanks for the review, Daryn. There's no easy way that I can see to know if the
DN's block contents were considered stale due to startup or having been made
active, as we only store a boolean in the DatanodeDescriptor indicating stale
or not. Though I agree it would be nice to have that log message differentiate
the reason for staleness, doesn't seem worth it to me to introduce a more
complex state system just to improve the log message.
I'm going to commit this momentarily.
> Standby NN will log that it has received a block report "after becoming
> active"
> -------------------------------------------------------------------------------
>
> Key: HDFS-4658
> URL: https://issues.apache.org/jira/browse/HDFS-4658
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
> Affects Versions: 2.0.4-alpha
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Priority: Trivial
> Attachments: HDFS-4658.patch
>
>
> Even when in the standby state the following line will sometimes be logged:
> {noformat}
> INFO blockmanagement.BlockManager: BLOCK* processReport: Received first block
> report from 172.21.3.106:50010 after becoming active. Its block contents are
> no longer considered stale
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
