[
https://issues.apache.org/jira/browse/HDFS-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HDFS-11193:
----------------------------
Attachment: HDFS-11193-HDFS-10285-00.patch
Attach initial patch where I've done the following changes:
# Added checks to handle the striped blocks. For a striped block, it needs to
construct internal block at the given index of a block group.
# Done refactoring of {{chooseTargetTypeInSameNode}} function. This has been
done to avoid choosing a target storage type node which already has the same
block. This is a generic case, which is common for continuous blocks and
striped blocks. For example, there are 3 nodes A(disk, disk), B(disk, disk),
C(disk, archive) and assume a block with storage locations A(disk), B(disk),
C(disk). Now, set policy as {{COLD}} and invoked {{#satisfyStoragePolicy}},
while choosing the target node for A, it shouldn't choose C.
> [SPS]: Erasure coded files should be considered for satisfying storage policy
> -----------------------------------------------------------------------------
>
> Key: HDFS-11193
> URL: https://issues.apache.org/jira/browse/HDFS-11193
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Rakesh R
> Assignee: Rakesh R
> Attachments: HDFS-11193-HDFS-10285-00.patch
>
>
> Erasure coded striped files supports storage policies {{HOT, COLD, ALLSSD}}.
> {{HdfsAdmin#satisfyStoragePolicy}} API call on a directory should consider
> all immediate files under that directory and need to check that, the files
> really matching with namespace storage policy. All the mismatched striped
> blocks should be chosen for block movement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
