[
https://issues.apache.org/jira/browse/HDDS-11403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Agrawal updated HDDS-11403:
---------------------------------
Component/s: OM
> PartialTableCache optimize for cleanup
> --------------------------------------
>
> Key: HDDS-11403
> URL: https://issues.apache.org/jira/browse/HDDS-11403
> Project: Apache Ozone
> Issue Type: Improvement
> Components: OM
> Reporter: Sumit Agrawal
> Assignee: Sumit Agrawal
> Priority: Major
>
> With reference to HDDS-11201, where FullTableCache clean optimization is
> done, similar mechanism is required for PartialTableCache.
> As OMStatemachine and DoubleBuffer maintains order of transaction applied
> over DB,
> * check for all transaction (epoch) is not required to be verified
> * And When higher epoch is received, this indicate all previous epoch cache
> can be cleaned up.
> Also in overload situation, and thread scheduling is slow, it can cause build
> of worker queue as in FullTableCache. The situation is less as there is no
> locking in this case.
> So as optimization, similar approach can be followed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
