[ 
https://issues.apache.org/jira/browse/HDFS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Allen Wittenauer resolved HDFS-153.
-----------------------------------

    Resolution: Fixed

This is probably stale.

Also, "Infinite Loop of Logging" is a terrible band name but probably a great 
religious text if you wanted to create a cult.

> NameNode entered into an infinite loop of logging
> -------------------------------------------------
>
>                 Key: HDFS-153
>                 URL: https://issues.apache.org/jira/browse/HDFS-153
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Runping Qi
>
> We have a cluster running Hadoop 0.19.0.
> For some reason, the name node entered into an infinite loop of spitting the 
> following message once every second:
> 2009-03-30 00:00:02,658 INFO 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: 
> commitBlockSynchronization(lastblock=blk_2800657178116909860_14611, 
> newgenerationstamp=0, newlength=0, newtargets=[])
> 2009-03-30 00:00:02,658 INFO org.apache.hadoop.ipc.Server: IPC Server handler 
> 4 on 8088, call commitBlockSynchronization(blk_2800657178116909860_14611, 0, 
> 0, false, true, [Lorg.apache.hadoop.hdfs.protocol.DatanodeID;@1558378) from 
> 10.126.185.32:45347: error: java.io.IOException: Block 
> (=blk_2800657178116909860_14611) not found
> java.io.IOException: Block (=blk_2800657178116909860_14611) 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.GeneratedMethodAccessor4.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)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to