[
https://issues.apache.org/jira/browse/HDFS-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Molkov updated HDFS-1024:
--------------------------------
Attachment: HDFS-1024.patch.1
Please see the new patch with your comments addressed.
It seems like throwing an exception with a meaningful text is the way to go for
a couple of reasons: you would not really run SecondaryNameNode and the
NameNode of different versions (or at least you shouldn't).
And with the check disabled there is a room for image corruption, which should
never be the case.
> 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, HDFS-1024.patch.1
>
>
> 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.
