Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 31 Jan 2013 02:13:13 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12602271.1344447542466.219945.1359598393530@arcas>
In-Reply-To: <JIRA.12602271.1344447542466@arcas>
References: <JIRA.12602271.1344447542466@arcas>
Subject: [jira] [Updated] (ACCUMULO-722) Accumulo using Accumulo as its own
 NameNode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Newton updated ACCUMULO-722:
---------------------------------

    Fix Version/s: 1.6.0
    
> Accumulo using Accumulo as its own NameNode
> -------------------------------------------
>
>                 Key: ACCUMULO-722
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-722
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>             Fix For: 1.6.0
>
>
> On large clusters, the NameNode can become a performance bottleneck.  The NameNode is also a single-point of failure.  Recent improvements to HDFS to support High Availability and Federation [See ACCUMULO-118] help address these issues, but at greater administrative costs and specialized hardware.
> We have seen demonstrations of using HBase to host a NameNode.  There's Aaron Cordova's example of a Distributed Name Node:
> [Design for a Distributed Name Node |http://www.slideshare.net/acordova00/design-for-a-distributed-name-node ]
> And giraffa:
> [Dynamic Namespace Partitioning with Giraffa File System |http://www.slideshare.net/Hadoop_Summit/dynamic-namespace-partitioning-with-giraffa-file-system]
> We could incrementally implement a self-hosted Accumulo, which would run as its own NameNode.  This would be useful for large Accumulo installations.  Over the long term, we could incorporate all NameNode functions to provide a scalable, distributed NameNode for other large Hadoop installations.
> Hopefully the approach used could be trivially ported to HBase as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira