[HDDS-3329] Ozone cluster expansion: Block deletion mismatch

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.4.1
• Component/s: Ozone Datanode
• Labels: TriagePending
• Target Version/s: 2.0.0
• Assignee: Lokesh Jain
• Reporter: Li Cheng
• Created: 02/Apr/20 11:47
• Updated: 16/Dec/23 23:43

Description

SCM logs keep printing this when we expand Ozone cluster with more datanodes.

 

2020-04-02 19:45:42,745 [EventQueue-PendingDeleteStatusForPendingDeleteHandler] INFO org.apache.hadoop.hdds.scm.block.SCMBlockDeletingService: Block deletion txnID mismatch in datanode 1eacbd89-a835-438e-aa4b-5bc78adb7c8c for containerID 314. Datanode delete txnID: 0, SCM txnID: 1208
2020-04-02 19:45:42,745 [EventQueue-PendingDeleteStatusForPendingDeleteHandler] INFO org.apache.hadoop.hdds.scm.block.SCMBlockDeletingService: Block deletion txnID mismatch in datanode 1eacbd89-a835-438e-aa4b-5bc78adb7c8c for containerID 351. Datanode delete txnID: 0, SCM txnID: 662
2020-04-02 19:45:42,745 [EventQueue-PendingDeleteStatusForPendingDeleteHandler] INFO org.apache.hadoop.hdds.scm.block.SCMBlockDeletingService: Block deletion txnID mismatch in datanode 1eacbd89-a835-438e-aa4b-5bc78adb7c8c for containerID 352. Datanode delete txnID: 0, SCM txnID: 1085