[
https://issues.apache.org/jira/browse/HDDS-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020882#comment-18020882
]
Priyesh K commented on HDDS-13601:
----------------------------------
We should not check duplicate transaction and blockId handling, this is as its
performance intensive operation and slow down delete block handling.
The control is already put at SCM for retry with timeout and chances of
occurrence is very rare.
So we need not handle this now.
> Enhance Duplicate Transaction handling logic in DN
> --------------------------------------------------
>
> Key: HDDS-13601
> URL: https://issues.apache.org/jira/browse/HDDS-13601
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Priyesh K
> Assignee: Priyesh K
> Priority: Major
> Labels: pull-request-available
>
> *Duplicate Transaction Handling*
> Problem: The handler currently only checks for duplicate transaction IDs.
> Gap: When SCM retries a transaction, the DN may receive the same {{txnId}}
> again, even though it has already been processed.
> Solution:
> # Enhance the logic to check both {{delete_txn}} table and
> {{{}block_table{}}}.
> # This ensures we correctly identify if the transaction has already been
> applied, avoiding unnecessary re-processing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
