[
https://issues.apache.org/jira/browse/HDDS-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sadanand Shenoy updated HDDS-6139:
----------------------------------
Description: 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. (was: In the
current streaming code we maintain only one bufferList for retry. Buffers in
the list are removed only during watchForCommit. So it 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.)
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
