[
https://issues.apache.org/jira/browse/HDDS-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793433#comment-17793433
]
Uma Maheswara Rao G commented on HDDS-9696:
-------------------------------------------
I am not against to make it configurable. But this config seems like an
advanced config. Are you proposing any optimal default value here?
What changes you plan to do based on scale? I don't see any recommendations on
how to change this value based on scale.
> Add configuration for wait time after checking queue in DeleteCmdWorker
> -----------------------------------------------------------------------
>
> Key: HDDS-9696
> URL: https://issues.apache.org/jira/browse/HDDS-9696
> Project: Apache Ozone
> Issue Type: Improvement
> Components: DN
> Affects Versions: 1.3.0
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
> Attachments: image-2023-11-15-16-16-26-922.png
>
>
> Now the purpose of DeleteCmdWorker is to regularly execute the delete block
> command. It will detect it every 2 seconds, but this time is a fixed value.
> In other words, no matter how many blocks need to be deleted, it takes this
> time to detect, which is not good. We should make this value configurable to
> be more user-friendly.
> !image-2023-11-15-16-16-26-922.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
