[HDDS-8139] Datanodes should not drop block delete transactions based on transaction ID

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: Ozone Datanode
• Labels: pull-request-available
• Target Version/s: 1.4.0, 1.3.1
• Assignee: Sumit Agrawal
• Reporter: Ethan Rose
• Created: 10/Mar/23 21:03
• Updated: 24/Mar/23 20:31
• Resolved: 21/Mar/23 06:06

Description

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.

Issue Links

• relates to: HDDS-8228 Add metric for out of order/retried delete transactions
• links to: GitHub Pull Request #4384