You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/04/01 05:52:27 UTC

[jira] Commented: (HDFS-1024) SecondaryNamenode fails to checkpoint because namenode fails with CancelledKeyException

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

stack commented on HDFS-1024:
-----------------------------

All tests pass but the expected (?) fail of: "org.apache.hadoop.streaming.TestStreamingExitStatus"

I'd like to commit to 0.20 branch.  Do we have to run a vote or is evidence of corruption of fsimage enough of a reason?

> 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.20.1, 0.20.2, 0.20.3, 0.21.0, 0.22.0
>            Reporter: dhruba borthakur
>            Assignee: Dmytro Molkov
>            Priority: Blocker
>             Fix For: 0.22.0
>
>         Attachments: HDFS-1024.patch, HDFS-1024.patch.1, HDFS-1024.patch.1-0.20.txt
>
>
> 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.