[
https://issues.apache.org/jira/browse/HDFS-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400030#comment-15400030
]
Kai Zheng commented on HDFS-7343:
---------------------------------
Yeah, I know the both issues. HDFS-10285 could be regarded as an improvement to
the storage policy support, allowing users to call some command or API to force
to enforce some policy on some files. This effort attempted to solve such
questions: What files become hot or cold, or in whatever conditions they
changed, so need to adjust storage policy/option for them? How do I know what
storage policy to set? What file forms to use, 3-replica or striping? And so
on. To answer such questions accurately and recommend storage option/policy
adjustments for uncertain files in a cluster smartly, it must collect facts
data across a cluster during some time, which must happen in a much larger
scope and effort.
> A comprehensive and flexible storage policy engine
> --------------------------------------------------
>
> Key: HDFS-7343
> URL: https://issues.apache.org/jira/browse/HDFS-7343
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Kai Zheng
> Assignee: Kai Zheng
>
> As discussed in HDFS-7285, it would be better to have a comprehensive and
> flexible storage policy engine considering file attributes, metadata, data
> temperature, storage type, EC codec, available hardware capabilities,
> user/application preference and etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
