[
https://issues.apache.org/jira/browse/HDFS-13655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501030#comment-16501030
]
Íñigo Goiri edited comment on HDFS-13655 at 6/4/18 11:36 PM:
-------------------------------------------------------------
We could also use this branch to take the {{ClientProtocol}} implementation
into a separate module like we did with {{RouterNamenodeProtocol}}.
Another issue is that the listing operations should be fairly simple.
However, the write ones would need some fanciness to decide where to do it.
We probably should split each subtask into READ and WRITE.
Anyway, if anybody has the time/need to start this, we can start defining the
way to implement the WRITE and then follow-up with defining each sub-task.
was (Author: elgoiri):
We could also use this branch to take the {{ClientProtocol}} implementation
into a separate module like we did with {{RouterNamenodeProtocol}}.
> RBF: Adding missing ClientProtocol methods to RBF
> -------------------------------------------------
>
> Key: HDFS-13655
> URL: https://issues.apache.org/jira/browse/HDFS-13655
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Xiao Chen
> Priority: Major
>
> As discussed with [~elgoiri], there are some HDFS methods that does not take
> path as a parameter. We should support these to work with federation.
> The ones missing are:
> * Snapshots
> * Storage policies
> * Encryption zones
> * Cache pools
> One way to reasonably have them to work with federation is to 'list' each
> nameservice and concat the results. This can be done pretty much the same as
> {{refreshNodes()}} and it would be a matter of querying all the subclusters
> and aggregate the output (e.g., {{getDatanodeReport()}}.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
