[
https://issues.apache.org/jira/browse/HADOOP-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657282#action_12657282
]
Brian Bockelman commented on HADOOP-4866:
-----------------------------------------
I do have HADOOP-4257 applied.
Second patch does not work; it's trying to match an exception's string, and
it's looking for the wrong string. The correct line should be:
if (ioe.getMessage().startsWith("java.io.IOException: " + block + " is
already commited")) {
With that fix, the DataNode gets the following message first at a high rate,
then settles to around 1HZ:
2008-12-16 22:32:55,524 INFO org.apache.hadoop.hdfs.server.datanode.DataNode:
Client calls recoverBlock(block=blk_8418325005865976265_90286,
targets=[172.16.1.124:50010])
> 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
> Attachments: 4866_20081215.patch, 4866_20081216.patch
>
>
> 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.
