[
https://issues.apache.org/jira/browse/HDFS-11163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901821#comment-15901821
]
Surendra Singh Lilhore commented on HDFS-11163:
-----------------------------------------------
Hi [~cnauroth],
bq. The logic is looking good to me, but I'd still like a second opinion review
before committing anything.
Based on [~vinayrpet] last [comment |
https://issues.apache.org/jira/browse/HDFS-11163?focusedCommentId=15889838&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15889838],
I feel he is okay with this logic..
> Mover should move the file blocks to default storage once policy is unset
> -------------------------------------------------------------------------
>
> Key: HDFS-11163
> URL: https://issues.apache.org/jira/browse/HDFS-11163
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer & mover
> Affects Versions: 2.8.0
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
> Attachments: HDFS-11163-001.patch, HDFS-11163-002.patch,
> HDFS-11163-003.patch, HDFS-11163-004.patch, HDFS-11163-005.patch,
> HDFS-11163-006.patch, temp-YARN-6278.HDFS-11163.patch
>
>
> HDFS-9534 added new API in FileSystem to unset the storage policy. Once
> policy is unset blocks should move back to the default storage policy.
> Currently mover is not moving file blocks which have zero storage ID
> {code}
> // currently we ignore files with unspecified storage policy
> if (policyId == HdfsConstants.BLOCK_STORAGE_POLICY_ID_UNSPECIFIED) {
> return;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
