[
https://issues.apache.org/jira/browse/HDFS-8480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648076#comment-14648076
]
Colin Patrick McCabe commented on HDFS-8480:
--------------------------------------------
Good catch, [~mingma]. If we make a change later to the edit log format, this
test will break because we'll be writing out an edit log with the new format,
but the old version ID.
I think we should simply check in a small binary edit log in order to do this
testing. This is similar to what we do with other "ugprade scenario" tests.
As [~zhz] mentioned, it would be a lot of effort to support writing out edit
logs in older formats (we have literally dozens of versions).
> Fix performance and timeout issues in HDFS-7929 by using hard-links to
> preserve old edit logs instead of copying them
> ---------------------------------------------------------------------------------------------------------------------
>
> 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
> Fix For: 2.7.1
>
> Attachments: HDFS-8480.00.patch, HDFS-8480.01.patch,
> HDFS-8480.02.patch, HDFS-8480.03.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)
