hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9411) HDFS ZoneLabel support
Date Sun, 22 Nov 2015 07:09:11 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020880#comment-15020880

Vinayakumar B commented on HDFS-9411:

bq. Hi Vinayakumar B, can you please clear the difference between ZoneLabel and colocation
in HDFS-9355?
HDFS-9355, indicates about storing different files from same client, in same datanodes.
This Jira proposes for the partition of datanodes to multiple zones, which might look like
colocation if number of datanodes in a zone are nearly equal to replication factor.
But, according to HDFS-9355, is entirely client-side changes.

> HDFS ZoneLabel 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: 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
> 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.

This message was sent by Atlassian JIRA

View raw message