[
https://issues.apache.org/jira/browse/HDFS-15083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011798#comment-17011798
]
Wei-Chiu Chuang commented on HDFS-15083:
----------------------------------------
Also, the existing trash implementation is pluggable, with the default
implementation TrashPolicyDefault.
This patch changes that behavior. While I am not aware of any one using
non-default trash implementation, we do have users requesting enhancement to
the existing trash behavior to support more complex use cases (e.g.
configurable trash root directory)
> 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: 2.10.0, 3.2.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: [email protected]
For additional commands, e-mail: [email protected]
