[
https://issues.apache.org/jira/browse/HDFS-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103962#comment-16103962
]
Chen Liang commented on HDFS-12195:
-----------------------------------
Appears to me that the idea of having {{KeySpaceManager#listKeys(keyPrefix,
maxKeys)}} is that, we need a way to list all keys that start with a special
prefix i.e. #deleting# for ALL volumes and buckets. While current listKeys are
listing keys within a particular volume+bucket prefix, and requires to specify
a volume and bucket. It also appears to me that the only reason why this is in
KeySpaceManager is to help unit test. I think an alternative way to do unit
test can be directly calling the metaStore's new {{listKeys(String keyPrefix,
int maxKeys)}}, then we don't need this call from KeySpaceManager.
> Ozone: DeleteKey-1: KSM replies delete key request asynchronously
> -----------------------------------------------------------------
>
> Key: HDFS-12195
> URL: https://issues.apache.org/jira/browse/HDFS-12195
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Weiwei Yang
> Assignee: Yuanbo Liu
> Attachments: client-ksm.png, HDFS-12195-HDFS-7240.001.patch,
> HDFS-12195-HDFS-7240.002.patch
>
>
> We will implement delete key in ozone in multiple child tasks, this is 1 of
> the child task to implement client to scm communication. We need to do it in
> async manner, once key state is changed in ksm metadata, ksm is ready to
> reply client with a successful message. Actual deletes on other layers will
> happen some time later.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
