Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 8 Nov 2013 16:56:19 +0000 (UTC)
From: "Milind Bhandarkar (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12678130.1383873841292.43049.1383929779749@arcas>
In-Reply-To: <JIRA.12678130.1383873841292@arcas>
References: <JIRA.12678130.1383873841292@arcas>
Subject: [jira] [Commented] (HDFS-5477) Block manager as a service
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Milind Bhandarkar commented on HDFS-5477:
-----------------------------------------

This is excellent direction, and in the same spirit as pluggability of namespaces. Looking forward to design docs.

> Block manager as a service
> --------------------------
>
>                 Key: HDFS-5477
>                 URL: https://issues.apache.org/jira/browse/HDFS-5477
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>
> The block manager needs to evolve towards having the ability to run as a standalone service to improve NN vertical and horizontal scalability.  The goal is reducing the memory footprint of the NN proper to support larger namespaces, and improve overall performance by decoupling the block manager from the namespace and its lock.  Ideally, a distinct BM will be transparent to clients and DNs.


--
This message was sent by Atlassian JIRA
(v6.1#6144)