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 "Andrew Schiefelbein (JIRA)" <ji...@apache.org> on 2017/12/21 17:25:06 UTC

[jira] [Updated] (HDFS-12957) Multi master name node

     [ https://issues.apache.org/jira/browse/HDFS-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Schiefelbein updated HDFS-12957:
---------------------------------------
    Priority: Minor  (was: Major)

> Multi master name node
> ----------------------
>
>                 Key: HDFS-12957
>                 URL: https://issues.apache.org/jira/browse/HDFS-12957
>             Project: Hadoop HDFS
>          Issue Type: Wish
>          Components: namenode
>    Affects Versions: 3.0.0
>         Environment: Multi node high availability with high throughput
>            Reporter: Andrew Schiefelbein
>            Priority: Minor
>
> While I do appreciate that the HA and federated setups do take care of some of the issues running in a multi node distributed fault tolerant way I believe that a singe name node is a bit of a pain point for me.
> My wish, and your mileage may vary, is that here could be a name node on each data node system so that each system could act as a gateway and worker for the cluster.
> In my tests right now I can push nearly 2 million records / second through a single node instance, but when I bring up 4 more nodes it doesn't go 4x faster as it has to retrieve from the name node and go through it as a gateway to the cluster.  For speed and resiliency if this could be spread out among n number of nodes and put behind a load balancer it would be the ideal solution for distributed resilient and high throughput shared storage. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org