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] Commented: (HDFS-1024) SecondaryNamenode fails to checkpoint because namenode fails with CancelledKeyException
Date Thu, 01 Apr 2010 13:14:28 GMT

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

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

Well spotted Dhruba.

So, the scenario is an updated 2NN but NN has not been updated (or vice-versa)?  My guess
would be that the incidence of NNs not being updated in tandem is low to zero.  If this is
true, would a release note to the effect that both NNs must be updated together be patch enough
to cover the low incidence of encounters of this incompatible change?

> 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