[
https://issues.apache.org/jira/browse/HDFS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038518#comment-13038518
]
ramkrishna.s.vasudevan commented on HDFS-1989:
----------------------------------------------
Why does saveNameSpace api closes all the editLog Streams.
Ideally once checkpoint starts the streams have already been diverted to
edit.new and the in saveCheckpoint we try to move the current directory
contents to latestcheckpoint.tmp.
So in what scneario do we require the editLog.close() which results in closing
of all edit streams?
> 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
