This is related to HADOOP-1076.
--Konstantin
Dhruba Borthakur wrote:
This message gets printed if a previous attempt to merge the Transaction log
with the fsimage fails.
The SecondaryNameNode periodically tries to merge the fsimage and the
fsedits file and creates a new fsimage. If this process fails in the middle
(due to whatever reason), the Namenode is left with fsedits and fsedits.new.
Now, future attempts by the SecondarynameNode to merge fsimage and fsedits
prints out the message that you are seeing.
The log message is not harmful per se, but if you want to get rid of it, you
would have to restart your NameNode.
Thanks,
dhruba
-----Original Message-----
From: Phantom [mailto:[EMAIL PROTECTED]
Sent: Friday, June 22, 2007 10:09 AM
To: [email protected]
Subject: What is the meaning of this exception ?`
I see a whole lot of this in my namenode log. Is this benign or is there
something something more sinister going on ? Why would this be happening ?
2007-06-21 00:16:24,782 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 1 on 9000, call rollEditLog() from 10.16.159.101:48099: 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 org.apache.hadoop.dfs.FSEditLog.rollEditLog(FSEditLog.java:467)
at org.apache.hadoop.dfs.FSNamesystem.rollEditLog(FSNamesystem.java
:3239)
at org.apache.hadoop.dfs.NameNode.rollEditLog(NameNode.java:544)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:341)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:573)
2007-06-21 00:21:24,818 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit
Log
Thanks
Avinash
