[
https://issues.apache.org/jira/browse/HDDS-13021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951036#comment-17951036
]
Wei-Chiu Chuang commented on HDDS-13021:
----------------------------------------
HDDS-11808 looks like the same bug.
> AbstractKeyDeletingService should have unique call id for each and every
> ratis request
> --------------------------------------------------------------------------------------
>
> Key: HDDS-13021
> URL: https://issues.apache.org/jira/browse/HDDS-13021
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Swaminathan Balachandran
> Assignee: Swaminathan Balachandran
> Priority: Major
> Labels: pull-request-available
>
> Currently AbstractKeyDeletingService can only submit one ratis request for
> one task instead of that there should be a monotonically increasing callId
> for each and every ratis request submitted by the client instead of depending
> on the runCount. This can impact in SnapshotDeletingService background
> service which as of date even though submits multiple requests in one run but
> only one ratis request gets accepted in one run. Preventing the service from
> scaling when there are a lot of snapshots that need to be purged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
