[
https://issues.apache.org/jira/browse/HDDS-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-13363:
-------------------------------
Description:
We need to add guardrails to ensure that all the OM cache added by the OM
request will be cleaned up later by the OzoneManagerDoubleBuffer which detected
the cache by using @CleanupTableInfo annotation. This is to prevent memory leak
due to uncollected expired cache entries. Uncollected expired cache entries
might also cause stale reads.
OM Table Cache leaks could result in the following issues
* Gradual increase in OM heap memory: This increase is usually gradual and not
noticeable since there are no exceptions when a cache entry is not cleaned up.
* Increased latency in some operations: OM operations like listKeys need to
iterate both the cache and underlying RocksDB table. Having a lot of cache
entries might cause increase overall latency.
was:
We need to add guardrails to ensure that all the OM cache added by the OM
request will be cleaned up later by the OzoneManagerDoubleBuffer which detected
the cache by using @CleanupTableInfo annotation. This is to prevent memory leak
due to uncollected expired cache entries. Uncollected expired cache entries
might also cause stale reads.
OM Table Cache leaks could result in the following issues
* Gradual increase in OM heap memory: This increase is usually gradual and not
noticeable since there are no exceptions when a cache entry is not cleaned up.
> Prevent OM Table Cache Leak
> ---------------------------
>
> Key: HDDS-13363
> URL: https://issues.apache.org/jira/browse/HDDS-13363
> Project: Apache Ozone
> Issue Type: Improvement
> Components: OM
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> We need to add guardrails to ensure that all the OM cache added by the OM
> request will be cleaned up later by the OzoneManagerDoubleBuffer which
> detected the cache by using @CleanupTableInfo annotation. This is to prevent
> memory leak due to uncollected expired cache entries. Uncollected expired
> cache entries might also cause stale reads.
> OM Table Cache leaks could result in the following issues
> * Gradual increase in OM heap memory: This increase is usually gradual and
> not noticeable since there are no exceptions when a cache entry is not
> cleaned up.
> * Increased latency in some operations: OM operations like listKeys need to
> iterate both the cache and underlying RocksDB table. Having a lot of cache
> entries might cause increase overall latency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
