Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Wed, 4 Feb 2015 21:13:35 +0000 (UTC)
From: "Ray (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12772496.1423084362000.257939.1423084415353@Atlassian.JIRA>
In-Reply-To: <JIRA.12772496.1423084362000@Atlassian.JIRA>
References: <JIRA.12772496.1423084362000@Atlassian.JIRA>
 <JIRA.12772496.1423084362926@arcas>
Subject: [jira] [Created] (HDFS-7737) Implement distributed namenode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ray created HDFS-7737:
-------------------------

             Summary: Implement distributed namenode
                 Key: HDFS-7737
                 URL: https://issues.apache.org/jira/browse/HDFS-7737
             Project: Hadoop HDFS
          Issue Type: New Feature
            Reporter: Ray
            Assignee: Ray
            Priority: Minor


Try to add the following functions on HDFS:
1) Manually move metadata across different name nodes, without losing the original data locality
2) Automatically balance metadata across different name nodes with a novel subtree partition algorithm
3) Able to set a replication factor number for each name node, and each replicated name node can balance live read/write traffic
4) All the functionalities above are highly configurable, and the administrator can decide if he wants to use distributed name node setup or just HDFS federation


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)