[
https://issues.apache.org/jira/browse/HDFS-8538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606094#comment-14606094
]
Arpit Agarwal commented on HDFS-8538:
-------------------------------------
bq. This leads me to an potential enhancement: count the # of outstanding
writes to a low-capacity disk, and exclude it from skewed placement if it's got
too many outstanding writes. This would be even better if we used OS-level IO
statistics, but that could be a follow-on.
Hi Andrew, incorporating load information would address my concern about
hotspots. OS-level stats are better so we account for non-dfs disk load.
> Change the default volume choosing policy to
> AvailableSpaceVolumeChoosingPolicy
> -------------------------------------------------------------------------------
>
> Key: HDFS-8538
> URL: https://issues.apache.org/jira/browse/HDFS-8538
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.7.0
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Attachments: hdfs-8538.001.patch
>
>
> For datanodes with different sized disks, they almost always want the
> available space policy. Users with homogenous disks are unaffected.
> Since this code has baked for a while, let's change it to be the default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
