[
https://issues.apache.org/jira/browse/HDFS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053285#comment-13053285
]
ramkrishna.s.vasudevan commented on HDFS-1989:
----------------------------------------------
Here in what scenario is it necessary to close the editLogs while saving the
name space.
W.r.t backup namenode already the edits.new streams has been opened and it is
not present in the current directory.
Is there any scenario where the editLogs.close() has to be called?
Can we add an additional api which does not have this editLogs.close() and call
it in checkpointflow alone?
Pls correct me if am wrong.
> 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
