You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2022/09/08 21:24:00 UTC
[jira] [Resolved] (HDDS-4120) Implement cleanup service for OM open key table
[ https://issues.apache.org/jira/browse/HDDS-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose resolved HDDS-4120.
------------------------------
Fix Version/s: 1.3.0
Resolution: Fixed
Hi [~ckj] [~micahzhao] I'm resolving this Jira since all the subtasks are implemented. If you would like to add more tasks we can re-open this Jira or start a new one. Thanks for the work!
> Implement cleanup service for OM open key table
> -----------------------------------------------
>
> Key: HDDS-4120
> URL: https://issues.apache.org/jira/browse/HDDS-4120
> Project: Apache Ozone
> Issue Type: New Feature
> Components: OM HA
> Reporter: Ethan Rose
> Assignee: Ethan Rose
> Priority: Major
> Fix For: 1.3.0
>
>
> Currently, uncommitted keys in the OM open key table remain there until they are committed. A background service should periodically run to remove open keys and their associated blocks from memory if the key is past a certain age. This value will be configurable with the existing ozone.open.key.expire.threshold setting, which currently has a default value of 1 day. Any uncommitted key in the open key table older than this will be marked for deletion, and cleaned up with the existing OM key deleting service. A configurable value should limit the number of open keys that can be removed in one run of the service.
> [Design Document|https://docs.google.com/document/d/1pEczSN8O0T60UMHF2GYX0PJbfzpaHPTbsEkOoBdBwQE/edit?usp=sharing]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org