[
https://issues.apache.org/jira/browse/HDFS-11163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815949#comment-15815949
]
Chris Nauroth commented on HDFS-11163:
--------------------------------------
bq. we can add one API to get default policy from namenode, so we can avoid
getStoragePolicy RPC per file.
If we went in this direction, then maybe it could fit into
{{getServerDefaults}}.
However, I think the challenge is that it really needs to be sensitive to path.
If the storage policy is unspecified at an inode, then the real effective
storage policy might be resolved via inheritance from the inode's ancestry. I
can't think of a clever way to completely avoid additional RPCs, though perhaps
a new API could help reduce it by memoizing results from the ancestry on the
client side.
This is tricky. Sorry I missed it in the review of HDFS-9534.
> 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-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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
