You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Sadanand Shenoy (Jira)" <ji...@apache.org> on 2023/05/25 05:24:00 UTC

[jira] [Commented] (HDDS-5852) Optimize streaming chunk write on exception

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

Sadanand Shenoy commented on HDDS-5852:
---------------------------------------

Eg :  Say chunk1 chunk2 chunk3 is written and during chunk4 there is an exception, During retry we start again with chunk1 chunk2 chunk3 but they have already been written once , Instead of writing these 3 chunks again , do a put block for these 3 chunks and write the 4th chunk in a different pipeline (say if container/pipeline closed exception)

> Optimize streaming chunk write on exception
> -------------------------------------------
>
>                 Key: HDDS-5852
>                 URL: https://issues.apache.org/jira/browse/HDDS-5852
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone Client
>            Reporter: Shashikant Banerjee
>            Assignee: Sadanand Shenoy
>            Priority: Major
>
> Currently, with HDDS-5674 on retry , the data is rewritten from the last acknowledged putBlock commit . As an optimization, putBlock should first be executed for the length of the last acknowledged streaming write and then remaining data in the buffers should be rewritten on a different pipeline.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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