[
https://issues.apache.org/jira/browse/HDFS-9411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902964#comment-15902964
]
Rakesh R commented on HDFS-9411:
--------------------------------
bq. But the block re replication wont consider/honor this favored nodes ?
[~anoop.hbase], With the favored nodes, block will be pinned at the datanodes
to prevent mover/balancer tool operations. Since the favored nodes information
is not persisted in HDFS(Namenode), during replication these blocks will be
re-replicated to new datanodes. I hope the following link, [javadoc
DistributedFileSystem#create function with favored
nodes|https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/DistributedFileSystem.java#L390]
will give you better clarity about the current behaviors.
> 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_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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
