hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-1024) SecondaryNamenode fails to checkpoint because namenode fails with CancelledKeyException
Date Wed, 31 Mar 2010 06:54:27 GMT

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

stack updated HDFS-1024:
------------------------

    Attachment: HDFS-1024.patch.1-0.20.txt

A patch for 0.20.

There doesn't seem to be any reason why 0.20 doesn't have the same issue (and so in 0.20 the
2NN could hand back half an fsimage).

Testing the patch now.  Will reporrt if all passes.

> 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.


Mime
View raw message