accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-722) Accumulo using Accumulo as its own NameNode
Date Wed, 08 Aug 2012 17:40:20 GMT
Eric Newton created ACCUMULO-722:
------------------------------------

             Summary: 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


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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message