[
https://issues.apache.org/jira/browse/HDFS-12742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303653#comment-16303653
]
Weiwei Yang commented on HDFS-12742:
------------------------------------
Hi [~shashikant]
Thanks for revisiting this.
bq. i think the better approach here would be to iterate through all the keys
and build the container list in KSM and send container deletion request to SCM
to delete the containers specific to the particular KSM instance directly at
SCM instead of sending key deletion request.
I can't see the difference of this approach comparing to directly sending key
deletion requests, they both need to iterate all keys. If a KSM has millions of
keys, it will be a very slow process. And it might need more than 1 day or 2
until all data actually gets deleted on datanodes. That was why I suggested to
operate on metadata level, that will be much faster.
Thanks
> Add support for KSM --expunge command
> -------------------------------------
>
> Key: HDFS-12742
> URL: https://issues.apache.org/jira/browse/HDFS-12742
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: HDFS-7240
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Fix For: HDFS-7240
>
> Attachments: HDFS-12742-HDFS-7240.001.patch,
> HDFS-12742-HDFS-7240.002.patch
>
>
> KSM --expunge will delete all the data from the data nodes for all the keys
> in the KSM db.
> User will have no control over the deletion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
