You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2022/01/14 14:47:00 UTC
[jira] [Resolved] (HDDS-6139) Fix incorrect computation of totalAckDataLength
[ https://issues.apache.org/jira/browse/HDDS-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz-wo Sze resolved HDDS-6139.
------------------------------
Fix Version/s: HDDS-4454
Resolution: Fixed
The pull request was merged. Thanks [~sadanand_shenoy]!
Thanks also [~shashikant] for reviewing and merging the pull request.
> Fix incorrect computation of totalAckDataLength
> -----------------------------------------------
>
> Key: HDDS-6139
> URL: https://issues.apache.org/jira/browse/HDDS-6139
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sadanand Shenoy
> Assignee: Sadanand Shenoy
> Priority: Major
> Labels: pull-request-available
> Fix For: HDDS-4454
>
>
> In the current streaming code we maintain only one bufferList for retry. Buffers in the list are removed only during watchForCommit. So there might occur a case if putBlock is followed by another putBlock the commitInfoMap has the same list for both indexes which will cause incorrect computation of totalAckDatalength which is used during retry.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org