[jira] [Updated] (ACCUMULO-722) Accumulo using Accumulo as its own NameNode

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

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

Christopher Tubbs updated ACCUMULO-722:
---------------------------------------

    Fix Version/s:     (was: 1.7.0)

> Accumulo using Accumulo as its own NameNode
> -------------------------------------------
>
>                 Key: ACCUMULO-722
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-722
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Eric Newton
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)