[
https://issues.apache.org/jira/browse/HDFS-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597778#comment-14597778
]
Hudson commented on HDFS-7929:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #235 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/235/])
HDFS-8480. Fix performance and timeout issues in HDFS-7929 by using hard-links
to preserve old edit logs, instead of copying them. (Zhe Zhang via Colin P.
McCabe) (cmccabe: rev 7b424f938c3c306795d574792b086d84e4f06425)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDFSUpgrade.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NNUpgradeUtil.java
> inotify unable fetch pre-upgrade edit log segments once upgrade starts
> ----------------------------------------------------------------------
>
> Key: HDFS-7929
> URL: https://issues.apache.org/jira/browse/HDFS-7929
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Zhe Zhang
> Assignee: Zhe Zhang
> Fix For: 2.7.0
>
> Attachments: HDFS-7929-000.patch, HDFS-7929-001.patch,
> HDFS-7929-002.patch, HDFS-7929-003.patch
>
>
> inotify is often used to periodically poll HDFS events. However, once an HDFS
> upgrade has started, edit logs are moved to /previous on the NN, which is not
> accessible. Moreover, once the upgrade is finalized /previous is currently
> lost forever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
