[ https://issues.apache.org/jira/browse/HDFS-11464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081493#comment-17081493 ]
Hadoop QA commented on HDFS-11464: ---------------------------------- | (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 8s{color} | {color:red} HDFS-11464 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-11464 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12867091/HDFS-11464.005.patch | | Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/29111/console | | Powered by | Apache Yetus 0.8.0 http://yetus.apache.org | This message was automatically generated. > Improve the selection in choosing storage for blocks > ---------------------------------------------------- > > Key: HDFS-11464 > URL: https://issues.apache.org/jira/browse/HDFS-11464 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: namenode > Reporter: Yiqun Lin > Assignee: Yiqun Lin > Priority: Major > Attachments: HDFS-11464.001.patch, HDFS-11464.002.patch, > HDFS-11464.003.patch, HDFS-11464.004.patch, HDFS-11464.005.patch > > > Currently the logic in choosing storage for blocks is not a good way. It > always uses the first valid storage of a given StorageType ({{see > DataNodeDescriptor#chooseStorage4Block}}). This should not be a good > selection. That means blcoks will always be written to the same volume (first > volume) and other valid volumes have no choices. This problem is brought up > by this comment ( > https://issues.apache.org/jira/browse/HDFS-9807?focusedCommentId=15878382&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15878382 > ) > There is one solution from me: > * First, based on existing storages in one node, extract all the valid > storages into a collection. > * Then, disrupt the order of these vaild storages, get a new collection. > * Finally, get the first storage from the new storages collection. > These steps will be executed in {{DataNodeDescriptor#chooseStorage4Block}} > and replace current logic. I think this improvement can be done as a subtask > under HDFS-11419. Any further comments are welcomed. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org