[
https://issues.apache.org/jira/browse/HADOOP-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HADOOP-4866:
-------------------------------------------
Attachment: 4866_20081217.patch
> Even with the second patch, the extremely high rate of the log messages in
> the NN still appear.
I think it will stable down. Does it?
> 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])
There is a DFSClient keeps calling recoverBlock(..). Could you find out the
corresponding DFSClient log messages to see why it keeps doing that?
Thanks a lot for your help on debugging this!
4866_20081217.patch: use contains(..) instead of startsWith(..).
> 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,
> 4866_20081217.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.
