[ 
https://issues.apache.org/jira/browse/HDFS-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150278#comment-16150278
 ] 

Weiwei Yang commented on HDFS-12235:
------------------------------------

Hi [~anu]

Could you please help to review the latest patch? I've been working on this 
with [~yuanbo] for a while, this is the last big piece of delete key work. With 
this patch, functionally delete key starts to work. Next week, I will setup a 
multi-nodes cluster to generate a large number of keys using corona and test 
this function in scale, there might be some more improvements or bug fixes but 
basic stuff should be ready now.

The test case failure TestKeys doesn't seem to be related to this patch, this 
test fails on recent jenkins runs even without the patch and could not be 
reproduced locally, might need another JIRA to track.

Please let me know your thoughts or suggestions. Thanks.

> Ozone: DeleteKey-3: KSM SCM block deletion message and ACK interactions
> -----------------------------------------------------------------------
>
>                 Key: HDFS-12235
>                 URL: https://issues.apache.org/jira/browse/HDFS-12235
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>    Affects Versions: HDFS-7240
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>         Attachments: HDFS-12235-HDFS-7240.001.patch, 
> HDFS-12235-HDFS-7240.002.patch, HDFS-12235-HDFS-7240.003.patch, 
> HDFS-12235-HDFS-7240.004.patch, HDFS-12235-HDFS-7240.005.patch
>
>
> KSM and SCM interaction for delete key operation, both KSM and SCM stores key 
> state info in a backlog, KSM needs to scan this log and send block-deletion 
> command to SCM, once SCM is fully aware of the message, KSM removes the key 
> completely from namespace. See more from the design doc under HDFS-11922, 
> this is task break down 2.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to