Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
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.