Ethan Rose created HDDS-8139:
--------------------------------
Summary: 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
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]
