[
https://issues.apache.org/jira/browse/HDFS-8578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591358#comment-14591358
]
Raju Bairishetti commented on HDFS-8578:
----------------------------------------
[~vinayrpet] I Agree, Making changes in BlockPoolSliceStorage won't help us in
improving the performance as
[HDFS-7035|https://issues.apache.org/jira/browse/HDFS-7035] makes the data
dir/disk processing atomic.
My bad, initially I was looking into the 2.6.0 branch. Changes in
BlockPoolSliceStorage would have been helpful only 2.6.0 branch. Lots of
refactoring happened as part of
[HDFS-7035|https://issues.apache.org/jira/browse/HDFS-7035]. It was merged to
*2.7.0 branch*.
> On upgrade, Datanode should process all storage/data dirs in parallel
> ---------------------------------------------------------------------
>
> Key: HDFS-8578
> URL: https://issues.apache.org/jira/browse/HDFS-8578
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Reporter: Raju Bairishetti
> Priority: Critical
> Attachments: HDFS-8578-01.patch, HDFS-8578-02.patch
>
>
> Right now, during upgrades datanode is processing all the storage dirs
> sequentially. Assume it takes ~20 mins to process a single storage dir then
> datanode which has ~10 disks will take around 3hours to come up.
> *BlockPoolSliceStorage.java*
> {code}
> for (int idx = 0; idx < getNumStorageDirs(); idx++) {
> doTransition(datanode, getStorageDir(idx), nsInfo, startOpt);
> assert getCTime() == nsInfo.getCTime()
> : "Data-node and name-node CTimes must be the same.";
> }
> {code}
> It would save lots of time during major upgrades if datanode process all
> storagedirs/disks parallelly.
> Can we make datanode to process all storage dirs parallelly?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
