Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 18 Mar 2015 00:19:39 +0000 (UTC)
From: "Zhe Zhang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12781861.1426267245000.125008.1426637979802@Atlassian.JIRA>
In-Reply-To: <JIRA.12781861.1426267245000@Atlassian.JIRA>
References: <JIRA.12781861.1426267245000@Atlassian.JIRA>
 <JIRA.12781861.1426267245894@arcas>
Subject: [jira] [Updated] (HDFS-7929) inotify unable fetch pre-upgrade edit
 log segments once upgrade starts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhe Zhang updated HDFS-7929:
----------------------------
    Attachment: HDFS-7929-003.patch

Fixing the test failure (the added test didn't clean up the cluster).

> 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
>         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)