You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "zhuqi (Jira)" <ji...@apache.org> on 2020/01/04 16:00:00 UTC
[jira] [Updated] (HDFS-15083) Add new trash rpc which move the
trash (mkdir and the rename) operation to the server side.
[ https://issues.apache.org/jira/browse/HDFS-15083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhuqi updated HDFS-15083:
-------------------------
Attachment: HDFS-15083.001.patch
Status: Patch Available (was: Open)
> Add new trash rpc which move the trash (mkdir and the rename) operation to the server side.
> -------------------------------------------------------------------------------------------
>
> Key: HDFS-15083
> URL: https://issues.apache.org/jira/browse/HDFS-15083
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: dfsclient, namenode, rbf
> Affects Versions: 3.2.0, 2.10.0
> Reporter: zhuqi
> Assignee: zhuqi
> Priority: Major
> Attachments: HDFS-15083.001.patch
>
>
> Now the rbf trash with multi cluster mounted in [HDFS-14117|https://issues.apache.org/jira/browse/HDFS-14117] , the solution is not graceful。
> If we can move the client side trash (mkdir and rename) to the server side, we can not only solve the problem gracefully, but also reduce the trash rpc load in server side to about %50 compare to the origin trash which call two times rpc(mkdir and rename).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org