accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-722) Accumulo using Accumulo as its own NameNode
Date Sat, 19 Apr 2014 03:45:20 GMT


Sean Busbey commented on ACCUMULO-722:

among recent changes in HDFS:

* HA NameNode (HDFS-3077)
* Pluggable locality / failure tolerances for NameNode (HDFS-385, HDFS-8468)
* Improving scalability of namespace operations (HDFS-5389) and block location mapping (HDFS-5711)

Could we please forgo this ticket in favor of interested parties working on relevant bits
within HDFS?

> Accumulo using Accumulo as its own NameNode
> -------------------------------------------
>                 Key: ACCUMULO-722
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Eric Newton
>             Fix For: 1.7.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 |
> And giraffa:
> [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
> Hopefully the approach used could be trivially ported to HBase as well.

This message was sent by Atlassian JIRA

View raw message