[jira] Created: (HADOOP-1510) java.io.IOException: Attempt to roll edit log but edits.new exists

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (HADOOP-1510) java.io.IOException: Attempt to roll edit log but edits.new exists

Markus Jelsma (Jira)
java.io.IOException: Attempt to roll edit log but edits.new exists
------------------------------------------------------------------

                 Key: HADOOP-1510
                 URL: https://issues.apache.org/jira/browse/HADOOP-1510
             Project: Hadoop
          Issue Type: Bug
          Components: dfs
    Affects Versions: 0.13.0
         Environment: linux
            Reporter: Michael Bieniosek


I updated to hadoop-0.13, deleted the dfs/ directory, formatted the namenode, and then brought the namenode up.  Before any datanodes connected, I got this in my datanode log:

2007-06-20 22:16:38,960 INFO org.apache.hadoop.ipc.Server: IPC Server handler 9 on 10000: starting
2007-06-20 22:16:43,226 WARN org.apache.hadoop.dfs.StateChange: DIR* FSDirectory.unprotectedDelete: failed to re
move /hadoop/mapred/system because it does not exist
2007-06-20 22:20:19,345 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
2007-06-20 22:25:19,440 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
2007-06-20 22:25:19,442 INFO org.apache.hadoop.ipc.Server: IPC Server handler 4 on 10000, call rollEditLog() fro
m x.x.44.136:35679: 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.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.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)


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (HADOOP-1510) java.io.IOException: Attempt to roll edit log but edits.new exists

Markus Jelsma (Jira)

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

Michael Bieniosek updated HADOOP-1510:
--------------------------------------

    Description:
I updated to hadoop-0.13, deleted the dfs/ directory, formatted the namenode, and then brought the namenode up.  Before any datanodes connected, I got this in my namenode log:

2007-06-20 22:16:38,960 INFO org.apache.hadoop.ipc.Server: IPC Server handler 9 on 10000: starting
2007-06-20 22:16:43,226 WARN org.apache.hadoop.dfs.StateChange: DIR* FSDirectory.unprotectedDelete: failed to re
move /hadoop/mapred/system because it does not exist
2007-06-20 22:20:19,345 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
2007-06-20 22:25:19,440 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
2007-06-20 22:25:19,442 INFO org.apache.hadoop.ipc.Server: IPC Server handler 4 on 10000, call rollEditLog() fro
m x.x.44.136:35679: 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.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.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)


  was:
I updated to hadoop-0.13, deleted the dfs/ directory, formatted the namenode, and then brought the namenode up.  Before any datanodes connected, I got this in my datanode log:

2007-06-20 22:16:38,960 INFO org.apache.hadoop.ipc.Server: IPC Server handler 9 on 10000: starting
2007-06-20 22:16:43,226 WARN org.apache.hadoop.dfs.StateChange: DIR* FSDirectory.unprotectedDelete: failed to re
move /hadoop/mapred/system because it does not exist
2007-06-20 22:20:19,345 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
2007-06-20 22:25:19,440 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
2007-06-20 22:25:19,442 INFO org.apache.hadoop.ipc.Server: IPC Server handler 4 on 10000, call rollEditLog() fro
m x.x.44.136:35679: 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.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.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)



> java.io.IOException: Attempt to roll edit log but edits.new exists
> ------------------------------------------------------------------
>
>                 Key: HADOOP-1510
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1510
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.13.0
>         Environment: linux
>            Reporter: Michael Bieniosek
>
> I updated to hadoop-0.13, deleted the dfs/ directory, formatted the namenode, and then brought the namenode up.  Before any datanodes connected, I got this in my namenode log:
> 2007-06-20 22:16:38,960 INFO org.apache.hadoop.ipc.Server: IPC Server handler 9 on 10000: starting
> 2007-06-20 22:16:43,226 WARN org.apache.hadoop.dfs.StateChange: DIR* FSDirectory.unprotectedDelete: failed to re
> move /hadoop/mapred/system because it does not exist
> 2007-06-20 22:20:19,345 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
> 2007-06-20 22:25:19,440 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
> 2007-06-20 22:25:19,442 INFO org.apache.hadoop.ipc.Server: IPC Server handler 4 on 10000, call rollEditLog() fro
> m x.x.44.136:35679: 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.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.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)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (HADOOP-1510) java.io.IOException: Attempt to roll edit log but edits.new exists

Markus Jelsma (Jira)
In reply to this post by Markus Jelsma (Jira)

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

Michael Bieniosek resolved HADOOP-1510.
---------------------------------------

    Resolution: Invalid

Oops, that would be a rogue secondary namenode.

> java.io.IOException: Attempt to roll edit log but edits.new exists
> ------------------------------------------------------------------
>
>                 Key: HADOOP-1510
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1510
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.13.0
>         Environment: linux
>            Reporter: Michael Bieniosek
>
> I updated to hadoop-0.13, deleted the dfs/ directory, formatted the namenode, and then brought the namenode up.  Before any datanodes connected, I got this in my namenode log:
> 2007-06-20 22:16:38,960 INFO org.apache.hadoop.ipc.Server: IPC Server handler 9 on 10000: starting
> 2007-06-20 22:16:43,226 WARN org.apache.hadoop.dfs.StateChange: DIR* FSDirectory.unprotectedDelete: failed to re
> move /hadoop/mapred/system because it does not exist
> 2007-06-20 22:20:19,345 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
> 2007-06-20 22:25:19,440 INFO org.apache.hadoop.fs.FSNamesystem: Roll Edit Log
> 2007-06-20 22:25:19,442 INFO org.apache.hadoop.ipc.Server: IPC Server handler 4 on 10000, call rollEditLog() fro
> m x.x.44.136:35679: 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.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.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)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.