[
https://issues.apache.org/jira/browse/HDDS-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-13817:
----------------------------------
Labels: pull-request-available (was: )
> Add fixed-delay scheduling mode to SCMBlockDeletingService
> ----------------------------------------------------------
>
> Key: HDDS-13817
> URL: https://issues.apache.org/jira/browse/HDDS-13817
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: ChenXi
> Assignee: ChenXi
> Priority: Major
> Labels: pull-request-available
>
> SCMBlockDeletingService uses BackgroundService to implement periodic task
> scheduling.
> BackgroundService currently executes at a fixed frequency. If a task takes
> longer than the interval, the next task will be executed immediately after
> the previous task completes.
> For SCMBlockDeletingService, when the deletedBlocks table contains a large
> amount of data, the DeletedBlockLogStateManager#getReadOnlyIterator call may
> take longer than the BackgroundService's interval. This can cause other
> operations, such as DeletedBlockLogImpl#onMessage, to be blocked on the
> DeletedBlockLogImpl#lock, resulting transactions status cannot be updated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
