[
https://issues.apache.org/jira/browse/HADOOP-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656734#action_12656734
]
Tsz Wo (Nicholas), SZE commented on HADOOP-4866:
------------------------------------------------
Checked the codes again, the primary datanode may call
commitBlockSynchronization(..) with newgenerationstamp=0, newlength=0,
newtargets=[] when syncList.isEmpty() is true. The problem may be due to the
block is deleted after block recovery begins.
> NameNode error in commitBlockSynchronization
> --------------------------------------------
>
> Key: HADOOP-4866
> URL: https://issues.apache.org/jira/browse/HADOOP-4866
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Brian Bockelman
>
> The NameNode continuously has an error in the commitBlockSynchronization.
> This happens for ~5 blocks at a rate of 5-10Hz. I have no idea when this
> started happening because this has been going on for days, well past the
> start of our current logs.
> This appears to be a new symptom in 0.19.0, but I have no idea what could be
> causing it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
