[
https://issues.apache.org/jira/browse/HDFS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038519#comment-13038519
]
ramkrishna.s.vasudevan commented on HDFS-1989:
----------------------------------------------
of syncs: 21 SyncTimes(ms): 130 176
2011-05-17 14:28:44,921 ERROR org.apache.hadoop.hdfs.server.namenode.FSEditLog:
Unable to sync edit log.
java.io.IOException: java.lang.IllegalStateException: !!! WARNING !!! File
system changes are not persistent. No journal streams.
at
org.apache.hadoop.hdfs.server.namenode.FSEditLog.logEdit(FSEditLog.java:1029)
at
org.apache.hadoop.hdfs.server.namenode.BackupImage.journal(BackupImage.java:247)
at
org.apache.hadoop.hdfs.server.namenode.BackupNode.journal(BackupNode.java:224)
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.WritableRpcEngine$Server.call(WritableRpcEngine.java:422)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1419)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1415)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1131)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1413)
at org.apache.hadoop.ipc.Client.call(Client.java:1052)
at
org.apache.hadoop.ipc.WritableRpcEngine$Invoker.invoke(WritableRpcEngine.java:250)
at $Proxy8.journal(Unknown Source)
at
org.apache.hadoop.hdfs.server.namenode.EditLogBackupOutputStream.send(EditLogBackupOutputStream.java:181)
at
org.apache.hadoop.hdfs.server.namenode.EditLogBackupOutputStream.flushAndSync(EditLogBackupOutputStream.java:155)
at
org.apache.hadoop.hdfs.server.namenode.EditLogOutputStream.flush(EditLogOutputStream.java:84)
at
org.apache.hadoop.hdfs.server.namenode.FSEditLog.logSync(FSEditLog.java:515)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.completeFile(FSNamesystem.java:1797)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.complete(NameNode.java:896)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hadoop.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:422)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1419)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1415)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1131)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1413)
> When checkpointing by backup node occurs parallely when a file is being
> closed by a client then Exception occurs saying no journal streams.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-1989
> URL: https://issues.apache.org/jira/browse/HDFS-1989
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: ramkrishna.s.vasudevan
> Fix For: 0.23.0
>
>
> Backup namenode initiates the checkpointing process.
> As a part of checkpointing based on the timestamp it tries to download the
> FSImage or use the existing one.
> Then it tries to save the FSImage.
> During this time it tries to close the editLog streams.
> Parallely when a client tries to close a file just after the checkpointing
> process closes the editLog Stream then we get an exception saying
> java.io.IOException: java.lang.IllegalStateException: !!! WARNING !!! File
> system changes are not persistent. No journal streams.
> Here the saveNameSpace api closes all the editlog streams resulting in this
> issue.
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
