hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuanbo Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12195) Ozone: DeleteKey-1: KSM replies delete key request asynchronously
Date Thu, 27 Jul 2017 10:55:02 GMT

    [ 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.
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?
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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message