[
https://issues.apache.org/jira/browse/HADOOP-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656515#action_12656515
]
Brian Bockelman commented on HADOOP-4866:
-----------------------------------------
Here is the error message I'm getting:
2008-12-14 18:43:37,884 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem:
commitBlockSynchronization(lastblock=blk_-1466661706312681205_91866,
newgenerationstamp=0, newlength=0, newtargets=[])
2008-12-14 18:43:37,884 INFO org.apache.hadoop.ipc.Server: IPC Server handler
33 on 9000, call commitBlockSynchronization(blk_-1466661706312681205_91866, 0,
0, false, true, [Lorg.apache.hadoop.hdfs.protocol.DatanodeID;@b4e602c) from
172.16.1.162:44797: error: java.io.IOException: Block
(=blk_-1466661706312681205_91866) not found
java.io.IOException: Block (=blk_-1466661706312681205_91866) not found
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.commitBlockSynchronization(FSNamesystem.java:1898)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.commitBlockSynchronization(NameNode.java:410)
at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:452)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:892)
> NameNode error in commitBlockSynchronization
> --------------------------------------------
>
> Key: HADOOP-4866
> URL: https://issues.apache.org/jira/browse/HADOOP-4866
> Project: Hadoop Core
> Issue Type: Bug
> 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.
