You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2022/06/20 02:18:00 UTC
[jira] [Resolved] (HDDS-4123) Integrate OM Open Key Cleanup Service Into Existing Code
[ https://issues.apache.org/jira/browse/HDDS-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
mingchao zhao resolved HDDS-4123.
---------------------------------
Resolution: Fixed
PR merged, Thanks [~ckj] and [~erose] for the work!
> Integrate OM Open Key Cleanup Service Into Existing Code
> --------------------------------------------------------
>
> Key: HDDS-4123
> URL: https://issues.apache.org/jira/browse/HDDS-4123
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: OM HA
> Reporter: Ethan Rose
> Assignee: Kaijie Chen
> Priority: Major
> Labels: pull-request-available
>
> Implement the `OpenKeyCleanupService` class, and start and stop the service in `KeyManagerImpl`. The following configurations will be added to specify the service's behavior:
> # ozone.open.key.cleanup.service.interval: Frequency the service should run.
> # ozone.open.key.expire.threshold: Time from creation after which an open key is deemed expired.
> # ozone.open.key.cleanup.limit.per.task: Maximum number of keys the service can mark for deletion on each run.
> Default values for these configurations will be chosen from HDFS data.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org