[
https://issues.apache.org/jira/browse/HDFS-9411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B updated HDFS-9411:
--------------------------------
Description:
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.
was:
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.
ZONE_LABELS can logically divide the cluster datanodes into multiple Zones.
High level design doc to follow soon.
> 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-20-06-2016.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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
