hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Shvachko <...@yahoo-inc.com>
Subject Re: Edits.new
Date Thu, 04 Oct 2007 21:37:38 GMT

It looks like you are running hadoop 0.14.
This bug is related to HADOOP-1076 imo.
I recommend to shut down secondary name-node first.
And the restart the main name-node at some point when you are not at 
risk to loose jobs.
You should restart the name-node with -upgrade, otherwise you can hit 
which is now fixed in 0.14, but I don't know whether you run this patch.
Let me know if it helps.



Christian Kunz wrote:

>Looks like I ran into something like HADOOP-1978 symptom:
>2007-10-04 20:51:24,197 INFO org.apache.hadoop.fs.FSNamesystem: Roll
>Edit Log from <IP4>
>2007-10-04 20:51:24,197 INFO org.apache.hadoop.ipc.Server: IPC Server
>handler 41 on <port>, call rollEditLog() from <IP4>:35246: error:
>java.io.IOException: Attempt to roll edit log but edits.new exists
>java.io.IOException: Attempt to roll edit log but edits.new exists
>        at
>        at
>        at org.apache.hadoop.dfs.NameNode.rollEditLog(NameNode.java:525)
>        at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
>        at
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:340)
>        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:609)
>This goes on for 20 hours now.
>Is there an easy way to salvage without losing data?

View raw message