[
https://issues.apache.org/jira/browse/HDDS-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyesh K updated HDDS-13601:
-----------------------------
Description:
*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.
was:
*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.
*Upgrade Handling with Block Size*
* New block size information has been included in delete transactions.
* To support backward compatibility, upgrade scenarios must be handled using
the newly added {{{}HDDSLayoutFeature{}}}.
* This guarantees that older data is still valid after the upgrade while
allowing newer block size details to be used.
*Unit Testing*
Add unit tests to cover:
* Duplicate transaction checks using {{delete_txn}} and {{{}block_table{}}}.
* Upgrade scenarios with {{HDDSLayoutFeature}} to validate block size handling.
> 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: [email protected]
For additional commands, e-mail: [email protected]
