Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 16 Jun 2011 03:57:47 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <283525121.9768.1308196667378.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <17678216.38937.1306238267462.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (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.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050207#comment-13050207 ] 

ramkrishna.s.vasudevan commented on HDFS-1989:
----------------------------------------------

Hi,

Yes. the editsLog.close() is the problem as it closes all the editStreams including the diverted editStreams.  


> 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