[
https://issues.apache.org/jira/browse/HDFS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HDFS-280.
-----------------------------------
Resolution: Won't Fix
I'm going to close this as Won't Fix. Sites that have large NNs will likely
deploy QJM or equiv, making this change unnecessary.
> Secondary Namenode: Limit number of retries when fsimage/edits transfer fails
> -----------------------------------------------------------------------------
>
> Key: HDFS-280
> URL: https://issues.apache.org/jira/browse/HDFS-280
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Koji Noguchi
> Priority: Minor
>
> When hitting HADOOP-3980, secondary namenode kept on pulling gigs of
> fsimage/edits every 10 minutes which slowed down the namenode significantly.
> When namenode is down, I'd like the secondary namenode to keep on retrying
> to connect. However, when pull/push of large files keep on failing, I'd like
> a upper limit on the number of retries. Either shutdown or sleep for
> _fs.checkpoint.period_ seconds.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
