You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2014/04/19 05:47:15 UTC
[jira] [Comment Edited] (ACCUMULO-722) Accumulo using Accumulo as
its own NameNode
[ https://issues.apache.org/jira/browse/ACCUMULO-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974709#comment-13974709 ]
Sean Busbey edited comment on ACCUMULO-722 at 4/19/14 3:46 AM:
---------------------------------------------------------------
among recent changes in HDFS:
* HA NameNode (HDFS-3077)
* Pluggable locality / failure tolerances (HDFS-385, HADOOP-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?
was (Author: busbey):
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: https://issues.apache.org/jira/browse/ACCUMULO-722
> 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 |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)