[
https://issues.apache.org/jira/browse/HDDS-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose updated HDDS-8139:
-----------------------------
Target Version/s: 1.4.0, 1.3.1 (was: 1.3.1)
> Datanodes should not drop block delete transactions based on transaction ID
> ---------------------------------------------------------------------------
>
> Key: HDDS-8139
> URL: https://issues.apache.org/jira/browse/HDDS-8139
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Datanode
> Reporter: Ethan Rose
> Assignee: Sumit Agrawal
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> Currently datanodes expect to receive delete transactions from SCM in
> ascending order. If they get a transaction less than the largest one they
> have seen, they will quietly drop it and respond with success to the SCM. In
> some corner cases it may be possible that transactions arrive out of order,
> so the datanodes should not depend on ordering to prevent a large backlog of
> duplicate delete transactions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
