[
https://issues.apache.org/jira/browse/HDFS-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977968#comment-13977968
]
Amir Langer commented on HDFS-5477:
-----------------------------------
Hi Milind,
I believe the work - though it is related, is not necessarily just parts of the
same solution.
Or to put it in a different way - Something like the fine grained locking can
have its own independent value regardless if the Block manager is separated
from the Namenode or not.
Daryn can elaborate, but AFAIK the fine grained locking piece of work is not a
significant change in itself and therefore does not need a separate branch.
> 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)
