Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <389898519.302941268782287545.JavaMail.jira@brutus.apache.org>
Date: Tue, 16 Mar 2010 23:31:27 +0000 (UTC)
From: "Dmytro Molkov (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1024) SecondaryNamenode fails to checkpoint
 because namenode fails with CancelledKeyException
In-Reply-To: <1911863287.106541267826007502.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dmytro Molkov commented on HDFS-1024:
-------------------------------------

Can anyone commit this?

> SecondaryNamenode fails to checkpoint because namenode fails with CancelledKeyException
> ---------------------------------------------------------------------------------------
>
>                 Key: HDFS-1024
>                 URL: https://issues.apache.org/jira/browse/HDFS-1024
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 0.22.0
>            Reporter: dhruba borthakur
>            Assignee: Dmytro Molkov
>             Fix For: 0.22.0
>
>         Attachments: HDFS-1024.patch, HDFS-1024.patch.1
>
>
> The secondary namenode fails to retrieve the entire fsimage from the Namenode. It fetches a part of the fsimage but believes that it has fetched the entire fsimage file and proceeds ahead with the checkpointing. Stack traces will be attached below.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.