hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "genericqa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13032) Make AvailableSpaceBlockPlacementPolicy more adaptive
Date Mon, 22 Jan 2018 06:21:00 GMT

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

genericqa commented on HDFS-13032:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} | {color:red}
HDFS-13032 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-13032 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12906595/HDFS-13032.001.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/22739/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Make AvailableSpaceBlockPlacementPolicy more adaptive
> -----------------------------------------------------
>
>                 Key: HDFS-13032
>                 URL: https://issues.apache.org/jira/browse/HDFS-13032
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 2.8.2
>            Reporter: Tao Jie
>            Priority: Major
>         Attachments: HDFS-13032.001.patch
>
>
> In a heterogeneous HDFS cluster, datanode capacity and usage are very different.
> Now we can use HDFS-8131, a usage-aware block placement policy to deal with the problem.
However, this policy could be more flexible.
> 1, The probability of a node with high usage being chosen is fixed once the parameter
is set. That is the probability is always the same no matter its usage is 90% or 70%. When
the usage of a node is close to full, its probability of being chosen should be lower.
> 2, When the difference of usage is below 5%(hard code), the two nodes are considered
the same usage. I think it's OK when usage is 30% and 35%, but when usage is 93% and 98%,
they should not be treated equally. The correction of probability could be more smooth.
> In my opinion, when we choose one node from two candidates (A: usage 30%, B: usage 60%),
we can calculate the probability according to the available storage. p(A) = 70%/(70% + 40%),
p(B) = 40% (70% +40%). When a node is close to full, the probability would be very small.
> Also we could have another factor to weaken this correctness, and make the modification
not so aggressive.
> Any thought? [~liushaohui]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
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