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 "Vinayakumar B (JIRA)" <ji...@apache.org> on 2017/08/21 11:58:01 UTC

[jira] [Updated] (HDFS-9411) HDFS NodeLabel support

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

Vinayakumar B updated HDFS-9411:
--------------------------------
    Attachment: HDFS Node Labels-21-08-2017.pdf

Updated the design based on above comments
Please review

> HDFS NodeLabel support
> ----------------------
>
>                 Key: HDFS-9411
>                 URL: https://issues.apache.org/jira/browse/HDFS-9411
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>         Attachments: HDFSNodeLabels-15-09-2016.pdf, HDFSNodeLabels-20-06-2016.pdf, HDFS Node Labels-21-08-2017.pdf, HDFS_ZoneLabels-16112015.pdf
>
>
> HDFS currently stores data blocks on different datanodes chosen by BlockPlacement Policy. These datanodes are random within the scope(local-rack/different-rack/nodegroup) of network topology. 
> In Multi-tenant (Tenant can be user/service) scenario, blocks of any tenant can be on any datanodes.
>  Based on applications of different tenant, sometimes datanode might get busy making the other tenant's application to slow down. It would be better if admin's have a provision to logically divide the cluster among multi-tenants.
> NodeLabels adds more options to user to specify constraints to select specific nodes with specific requirements.
> High level design doc to follow soon.



--
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