hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhe Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10967) Add configuration for BlockPlacementPolicy to avoid near-full DataNodes
Date Thu, 06 Oct 2016 16:43:21 GMT

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

Zhe Zhang updated HDFS-10967:
-----------------------------
    Description: 
Large production clusters are likely to have heterogeneous nodes in terms of storage capacity,
memory, and CPU cores. It is not always possible to proportionally ingest data into DataNodes
based on their remaining storage capacity. Therefore it's possible for a subset of DataNodes
to be much closer to full capacity than the rest.

This heterogeneity is most likely rack-by-rack -- i.e. _m_ whole racks of low-storage nodes
and _n_ whole racks of high-storage nodes. So It'd be very useful if we can lower the chance
for those near-full DataNodes to become destinations for the 2nd and 3rd replicas.

  was:
Large production clusters are likely to have heterogeneous nodes in terms of storage capacity,
memory, and CPU cores. It is not always possible to proportionally ingest data into DataNodes
based on their remaining storage capacity. Therefore it's possible for a subset of DataNodes
to be much closer to full capacity than the rest.

This heterogeneity is most likely rack-by-rack -- i.e. _m_ whole racks with low-storage nodes
and _n_ whole racks with high-storage nodes. So It'd be very useful if we can lower the chance
for those near-full DataNodes to become destinations for the 2nd and 3rd replicas.


> Add configuration for BlockPlacementPolicy to avoid near-full DataNodes
> -----------------------------------------------------------------------
>
>                 Key: HDFS-10967
>                 URL: https://issues.apache.org/jira/browse/HDFS-10967
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Zhe Zhang
>              Labels: balancer
>
> Large production clusters are likely to have heterogeneous nodes in terms of storage
capacity, memory, and CPU cores. It is not always possible to proportionally ingest data into
DataNodes based on their remaining storage capacity. Therefore it's possible for a subset
of DataNodes to be much closer to full capacity than the rest.
> This heterogeneity is most likely rack-by-rack -- i.e. _m_ whole racks of low-storage
nodes and _n_ whole racks of high-storage nodes. So It'd be very useful if we can lower the
chance for those near-full DataNodes to become destinations for the 2nd and 3rd replicas.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message