hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milind Bhandarkar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5477) Block manager as a service
Date Tue, 22 Apr 2014 21:20:25 GMT

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

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

Hello again,

Sorry to repeat my question. Does it make sense to do this Jira, fine-grained locking in Namenode,
and Pluggable Namespaces work on a separate branch, since it involves the same codebase, and
is a significant enough change ?

> 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
>         Attachments: Block Manager as a Service - Implementation decisions.pdf, Proposal.pdf,
Proposal.pdf, Remote BM.pdf, Standalone BM.pdf, Standalone BM.pdf, patches.tar.gz
>
>
> 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.2#6252)

Mime
View raw message