hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3765) Namenode INITIALIZESHAREDEDITS should be able to initialize all shared storages
Date Tue, 14 Aug 2012 20:13:38 GMT

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

Todd Lipcon updated HDFS-3765:

       Resolution: Fixed
    Fix Version/s: 2.2.0-alpha
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)
> Namenode INITIALIZESHAREDEDITS should be able to initialize all shared storages
> -------------------------------------------------------------------------------
>                 Key: HDFS-3765
>                 URL: https://issues.apache.org/jira/browse/HDFS-3765
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.1.0-alpha, 3.0.0
>            Reporter: Vinay
>            Assignee: Vinay
>             Fix For: 3.0.0, 2.2.0-alpha
>         Attachments: hdfs-3765-branch-2.txt, HDFS-3765.patch, HDFS-3765.patch, HDFS-3765.patch,
hdfs-3765.txt, hdfs-3765.txt, hdfs-3765.txt
> Currently, NameNode INITIALIZESHAREDEDITS provides ability to copy the edits files to
file schema based shared storages when moving cluster from Non-HA environment to HA enabled
> This Jira focuses on the following
> * Generalizing the logic of copying the edits to new shared storage so that any schema
based shared storage can initialized for HA cluster.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message