hadoop-hdfs-issues mailing list archives

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

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

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

Note though, that this patch doesn't fix the underlying issue (that might as well be a jetty
but of sending huge images) and only protects HDFS from corrupting the image in the case when
the partial image read will be valid and will substitute the current image after secondary
name node processes it.

> 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.2
>            Reporter: dhruba borthakur
>            Assignee: Dmytro Molkov
>         Attachments: HDFS-1024.patch
>
>
> 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