You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/01/08 17:50:50 UTC
[jira] [Commented] (HDFS-5734) A NN-internal RPC BM service
[ https://issues.apache.org/jira/browse/HDFS-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865628#comment-13865628 ]
jay vyas commented on HDFS-5734:
--------------------------------
Sorry to ask, but... whats "BM" ? Is that the BackupNameNode?
> A NN-internal RPC BM service
> ----------------------------
>
> Key: HDFS-5734
> URL: https://issues.apache.org/jira/browse/HDFS-5734
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Amir Langer
>
> Separate the BM from NN by running it with with its own thread-pool and RPC protocol but still in the same process as NN.
> NN and BM will in interact through some loopback call that will simulate a separate service.
> This sprint still assumes a one to one relation between NN and BM and does not split the BM to a separate process, only simulates such a split inside the same VM. This allows us to defer any configuration issue / Testing support / scripts changes to later tasks.
> This task will therefore also not handle any HA issue to the BM itself. It will, however, deal with having BM code actually running in a different thread to the NN code and will handle building the initialisation / lifecycle code to an independent BM.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)