[
https://issues.apache.org/jira/browse/HDFS-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300516#comment-16300516
]
Virajith Jalaparti edited comment on HDFS-10285 at 12/21/17 8:16 PM:
---------------------------------------------------------------------
Hi [~umamaheswararao], Thanks for the meeting summary. Having both the options
(SPS within NN and SPS as service) would be great.
bq. it may be necessary to start SPS RPC with its own IP:port (within NN or
outside), so clients can always talk to SPS on that port, irrespective of where
its running.
Quick question about this -- what are clients you are referring to here? Are
these for admin operations? If the SPS is going to run outside the NN, I would
think it is going to be decoupled from/not depend on the FSNamesystem lock and
the NN-DN heartbeat protocol. The current implementation/design has a tight
coupling between the SPS and both these components.
was (Author: virajith):
Hi [~umamaheswararao], Thanks for the meeting summary. Having both the options
(SPS within NN and SPS as service) would be great.
bq. it may be necessary to start SPS RPC with its own IP:port (within NN or
outside), so clients can always talk to SPS on that port, irrespective of where
its running.
Quick question about this: what are clients you are referring to here? Are
these for admin operations? If the SPS is going to run outside the NN, I would
think it is going to be decoupled from/not depend on the FSNamesystem lock and
the NN-DN heartbeat protocol. The current implementation/design has a tight
coupling between the SPS and both these components.
> Storage Policy Satisfier in Namenode
> ------------------------------------
>
> Key: HDFS-10285
> URL: https://issues.apache.org/jira/browse/HDFS-10285
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: datanode, namenode
> Affects Versions: HDFS-10285
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Attachments: HDFS-10285-consolidated-merge-patch-00.patch,
> HDFS-10285-consolidated-merge-patch-01.patch,
> HDFS-10285-consolidated-merge-patch-02.patch,
> HDFS-10285-consolidated-merge-patch-03.patch,
> HDFS-SPS-TestReport-20170708.pdf,
> Storage-Policy-Satisfier-in-HDFS-June-20-2017.pdf,
> Storage-Policy-Satisfier-in-HDFS-May10.pdf,
> Storage-Policy-Satisfier-in-HDFS-Oct-26-2017.pdf
>
>
> Heterogeneous storage in HDFS introduced the concept of storage policy. These
> policies can be set on directory/file to specify the user preference, where
> to store the physical block. When user set the storage policy before writing
> data, then the blocks could take advantage of storage policy preferences and
> stores physical block accordingly.
> If user set the storage policy after writing and completing the file, then
> the blocks would have been written with default storage policy (nothing but
> DISK). User has to run the ‘Mover tool’ explicitly by specifying all such
> file names as a list. In some distributed system scenarios (ex: HBase) it
> would be difficult to collect all the files and run the tool as different
> nodes can write files separately and file can have different paths.
> Another scenarios is, when user rename the files from one effected storage
> policy file (inherited policy from parent directory) to another storage
> policy effected directory, it will not copy inherited storage policy from
> source. So it will take effect from destination file/dir parent storage
> policy. This rename operation is just a metadata change in Namenode. The
> physical blocks still remain with source storage policy.
> So, Tracking all such business logic based file names could be difficult for
> admins from distributed nodes(ex: region servers) and running the Mover tool.
> Here the proposal is to provide an API from Namenode itself for trigger the
> storage policy satisfaction. A Daemon thread inside Namenode should track
> such calls and process to DN as movement commands.
> Will post the detailed design thoughts document soon.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
