[
https://issues.apache.org/jira/browse/HDDS-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733465#comment-17733465
]
ChenXi commented on HDDS-8875:
------------------------------
The [HDDS-8139] Datanodes should not drop block delete transactions based on
transaction ID implements the logic of not dropping out-of-order transactions
when DNs receive out-of-order transactions in the DeleteBlockCommandHandler
threads.
But the if we do not drop the out of order transactions, there will have much
duplicate transactions write to the DB ,especially when SCM sends duplicate
transactions to the DN for some reason, such as the DN was too late to tell the
SCM the transactions processing result. or the DN DeleteBlockCommandHandler
thread block cause by wait lock. SCM will send large number of duplicate
transactions.
We need a mechanism to reduce duplicate transactions written to the database
consuming IO resources.
> Reduce duplicate delete transactions write to the DB
> ----------------------------------------------------
>
> Key: HDDS-8875
> URL: https://issues.apache.org/jira/browse/HDDS-8875
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Datanode
> Reporter: ChenXi
> Assignee: ChenXi
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
