[
https://issues.apache.org/jira/browse/HDDS-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz-wo Sze updated HDDS-5852:
-----------------------------
Component/s: Ozone Client
Description: 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. (was: Curently, with https://issues.apache.org/jira/browse/HDDS-5674
on retry , the data is rewritten from the last acknowledged putBlock commit .
On exception during streaming writes, 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.)
Summary: Optimize streaming chunk write on exception (was: Ensure
putBlock gets executed on last acknowledged streaming chunk write on 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: [email protected]
For additional commands, e-mail: [email protected]
