Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 29 Apr 2011 18:20:10 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1955400170.12274.1304101210912.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-1052) HDFS scalability with multiple
 namenodes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas updated HDFS-1052:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.23.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I merged the changes from federation branch HDFS-1052 into trunk. Thanks every one for participating in the discussions and help move this issue forward.

> HDFS scalability with multiple namenodes
> ----------------------------------------
>
>                 Key: HDFS-1052
>                 URL: https://issues.apache.org/jira/browse/HDFS-1052
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.23.0
>
>         Attachments: Block pool proposal.pdf, HDFS-1052.3.patch, HDFS-1052.4.patch, HDFS-1052.5.patch, HDFS-1052.6.patch, HDFS-1052.patch, Mulitple Namespaces5.pdf, high-level-design.pdf
>
>
> HDFS currently uses a single namenode that limits scalability of the cluster. This jira proposes an architecture to scale the nameservice horizontally using multiple namenodes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira