[
https://issues.apache.org/jira/browse/HDDS-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose updated HDDS-4120:
-----------------------------
Description:
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]
was:
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/1UgXA27NGBMmTfvrImYgLQtiCfHqbFGDwv0JKv3pJH6E/edit?usp=sharing]
> Implement cleanup service for OM open key table
> -----------------------------------------------
>
> Key: HDDS-4120
> URL: https://issues.apache.org/jira/browse/HDDS-4120
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Components: OM HA
> Reporter: Ethan Rose
> Assignee: Ethan Rose
> Priority: Major
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
