[jira] [Updated] (HDFS-1989) When checkpointing by backup node occurs parallely when a file is being closed by a client then Exception occurs saying no journal streams.

["Allen Wittenauer (JIRA)" <ji...@apache.org>]

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

Allen Wittenauer updated HDFS-1989:
-----------------------------------
    Fix Version/s:     (was: 0.24.0)

> 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: namenode
>    Affects Versions: 0.23.0
>            Reporter: ramkrishna.s.vasudevan
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)