[
https://issues.apache.org/jira/browse/HDFS-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103060#comment-16103060
]
Yuanbo Liu commented on HDFS-12195:
-----------------------------------
[~anu]/[~cheersyang] Thanks for your review.
{quote}
OzoneConsts.java
{quote}
addressed.
{quote}
MetadataManagerImpl.java
{quote}
The keyName here is not a complete key name like "/volume/bucket/key", this
value comes from the client. that's why I sent volume and bucket name to
construct a complete key name. I use {{getDeletedKeyName(bye[] keyName)}} to
replace the old one, what's your thoughts?
{quote}
KeySpaceManagerImpl.java
{quote}
As [~cheersyang] suggested, we can use {{writeBatch}} instead because this
method is an atomic operation. Test case has been added in v2 patch.
> 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
>
>
> 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]
