[
https://issues.apache.org/jira/browse/HDFS-12742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226495#comment-16226495
]
Shashikant Banerjee commented on HDFS-12742:
--------------------------------------------
HI [~cheersyang],
Thinking of the Use Case, our idea is to extend SCM services to multiples
instances of KSM..i.e, one SCM instance will be shared among multiple KSMs.
In those cases, KSM --expunge of one instance of KSM should not impact the
performance of the data path corresponding to the other KSM instances. So, if
KSM --expunge just sends the deletion request to SCM and then actual deletion
happens asynchronously in the dataNodes without impacting the data path
performance for other KSMs, should do. It would also be a good idea to say, if
the the storage utilization exceeds a certain threshold, we can do deletion of
data at SCM more aggressively accordingly. What do you think?
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
