[
https://issues.apache.org/jira/browse/ACCUMULO-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432118#comment-13432118
]
Eric Newton edited comment on ACCUMULO-722 at 8/9/12 8:27 PM:
--------------------------------------------------------------
It kinda works... but it's very much a prototype.
I am able to run the accumulo continuous ingest test, and the verify map-reduce
without a name node running.
Lots to think about, like permissions, balancing, replication and even basic
schema is open for review/change.
This is based primarily on Aaron's prototype, with ideas taken from Giraffa for
cleanly wedging a proxy in for the NameNode. There are a few changes to
Accumulo-1.4 required, which are in the ACCUMULO-722 branch. Tested against
hadoop 1.0.3.
was (Author: ecn):
It kinda works... but it's very much a prototype.
I am able to run the accumulo continuous ingest test, and the verify map-reduce
without a name node running.
Lots to think about, like permissions, balancing, replication and even basic
schema is open for review/change.
> 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
