[
https://issues.apache.org/jira/browse/HDFS-8480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590891#comment-14590891
]
Colin Patrick McCabe commented on HDFS-8480:
--------------------------------------------
Hi [~zhz],
We have to distinguish between two cases where the edit log is read:
1. when the edit log is read NN during startup to catch up with edits that
didn't make it into the fsimage yet
2. when the NN reads the edit log to handle an inotify request
Case #1 should be validating that the version is the newest version, since the
upgrade process ensures this.
Case #2 should not, since otherwise we will fail when reading old edit logs.
> Fix performance and timeout issues in HDFS-7929: use hard-links instead of
> copying edit logs
> --------------------------------------------------------------------------------------------
>
> Key: HDFS-8480
> URL: https://issues.apache.org/jira/browse/HDFS-8480
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Zhe Zhang
> Assignee: Zhe Zhang
> Priority: Critical
> Attachments: HDFS-8480.00.patch, HDFS-8480.01.patch,
> HDFS-8480.02.patch
>
>
> HDFS-7929 copies existing edit logs to the storage directory of the upgraded
> {{NameNode}}. This slows down the upgrade process. This JIRA aims to use
> hard-linking instead of per-op copying to achieve the same goal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
