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

["Eric Newton (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567255#comment-13567255 ] 

Eric Newton commented on ACCUMULO-722:
--------------------------------------

We've gathered statistics on the number of NN write operations per second from an Accumulo instance running continuous ingest.  We are seeing 3-5 write updates to HDFS metadata per-node, per-second.  This implies that the NN becomes a limitation at 1200 to 2000 node range


                
> 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