[
https://issues.apache.org/jira/browse/HADOOP-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657028#action_12657028
]
Brian Bockelman commented on HADOOP-4866:
-----------------------------------------
No dice. Now we just get the commitBlockSynchronization message continuously:
2008-12-16 09:46:17,990 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem:
commitBlockSynchronization(lastblock=blk_5492981093339503298_94099,
newgenerationstamp=0, newlength=0, newtargets=[])
2008-12-16 09:46:17,991 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem:
commitBlockSynchronization(lastblock=blk_5492981093339503298_94099,
newgenerationstamp=0, newlength=0, newtargets=[])
2008-12-16 09:46:17,992 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem:
commitBlockSynchronization(lastblock=blk_5492981093339503298_94099,
newgenerationstamp=0, newlength=0, newtargets=[])
2008-12-16 09:46:17,993 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem:
commitBlockSynchronization(lastblock=blk_5492981093339503298_94099,
newgenerationstamp=0, newlength=0, newtargets=[])
That's happening at a rate of about 1 KHZ! Help!
Brian
> 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
>
>
> 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.
