hadoop-hdfs-issues mailing list archives

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

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

Todd Lipcon commented on HDFS-1024:
-----------------------------------

Does the servlet not set a Content-length HTTP header? Since we're using HTTP we might as
well include it there. Then the HTTP client can easily verify it without having to modify
CheckpointSignature

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