[
https://issues.apache.org/jira/browse/HDDS-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lokesh Jain updated HDDS-4366:
------------------------------
Fix Version/s: 1.1.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> SCM deletion service should delete configured number of blocks every interval
> -----------------------------------------------------------------------------
>
> Key: HDDS-4366
> URL: https://issues.apache.org/jira/browse/HDDS-4366
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: SCM
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> SCM service currently uses datanode's configuration to determine the number
> of blocks to delete every interval. It should have its own congifuration for
> maximum number of blocks to delete in every interval.
> Further it currently scans the entire DB to fetch block deletion
> transactions. This can be avoided with this approach. With this patch service
> would always fetch configured number of blocks from the db.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
