Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Wed, 2 Oct 2013 22:15:44 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12608193.1348030970136.3112.1380752144165@arcas>
In-Reply-To: <JIRA.12608193.1348030970136@arcas>
References: <JIRA.12608193.1348030970136@arcas>
Subject: [jira] [Resolved] (HDFS-3958) Integrate upgrade/finalize/rollback
 with external journals
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers resolved HDFS-3958.
----------------------------------

    Resolution: Duplicate

Resolving as a duplicate of HDFS-5138, which has a lot more discussion about how best to do this.

> Integrate upgrade/finalize/rollback with external journals
> ----------------------------------------------------------
>
>                 Key: HDFS-3958
>                 URL: https://issues.apache.org/jira/browse/HDFS-3958
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Todd Lipcon
>
> Currently the NameNode upgrade/rollback/finalize framework only supports local storage. With edits being stored in pluggable Journals, this could create certain difficulties - in particular, rollback wouldn't actually rollback the external storage to the old state.
> We should look at how to expose the right hooks to the external journal storage to snapshot/rollback/finalize.


--
This message was sent by Atlassian JIRA
(v6.1#6144)