You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ivan Andika (Jira)" <ji...@apache.org> on 2025/09/29 05:23:00 UTC
[jira] [Updated] (HDDS-13520) Always retry failed BlockDeleteTransactions in SCM BlockDeletingSerice.
[ https://issues.apache.org/jira/browse/HDDS-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Andika updated HDDS-13520:
-------------------------------
Parent: HDDS-11506
Issue Type: Sub-task (was: Improvement)
> Always retry failed BlockDeleteTransactions in SCM BlockDeletingSerice.
> -----------------------------------------------------------------------
>
> Key: HDDS-13520
> URL: https://issues.apache.org/jira/browse/HDDS-13520
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: Nandakumar
> Assignee: Nandakumar
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.1.0
>
>
> After the recent changes that was done in the block deletion code in SCM, we don't need to maintain retry count in SCM for block delete transactions.
>
> Edit:
> On second thought, we can keep the count for debugging purpose but we don't need to skip the transaction once it has reached certain number of retries.
>
> So, this change will retain the count but will remove the logic which marks the transaction as failed and option to reset the count (this is no longer required).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org