You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2025/01/09 08:31:00 UTC

[jira] [Resolved] (HDDS-12007) BlockDataStreamOutput should only send one PutBlock during close

     [ https://issues.apache.org/jira/browse/HDDS-12007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Attila Doroszlai resolved HDDS-12007.
-------------------------------------
    Fix Version/s: 2.0.0
       Resolution: Fixed

> BlockDataStreamOutput should only send one PutBlock during close
> ----------------------------------------------------------------
>
>                 Key: HDDS-12007
>                 URL: https://issues.apache.org/jira/browse/HDDS-12007
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone Datanode
>            Reporter: Ivan Andika
>            Assignee: Tsz-wo Sze
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>
> Currently, during close two PutBlock request will be sent
>  * executePutBlockClose: This uses the DataStreamOutput#writeAsync with StandardWriteOption.CLOSE as part of the HDDS-6500 improvements
>  ** This will call sendForward which will trigger ContainerStateMachine#link which will be processed like PutBlock
>  * putBlockAsync: This is a normal PutBlock request which is executed per block boundary (similar to Write Pipeline V1)
> We should only call executePutBlockClose during close. We can use ClientProtoUtils#getRaftClientReply to convert from DataStreamReply to RaftClientReply which we can use to derive the PutBlock response.



--
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