[
https://issues.apache.org/jira/browse/HDFS-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620075#comment-13620075
]
Hudson commented on HDFS-4658:
------------------------------
Integrated in Hadoop-trunk-Commit #3548 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/3548/])
HDFS-4658. Standby NN will log that it has received a block report "after
becoming active". Contributed by Aaron T. Myers. (Revision 1463643)
Result = SUCCESS
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1463643
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
> 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
> Fix For: 2.0.5-beta
>
> 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