Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Implement continuous revision GC cleaning up documents older than a given threshold (e.g. one day). This issue is related to OAK-3070 where each GC run starts where the last one finished.
This will avoid peak load on the system as we see it right now, when GC is triggered once a day.
Attachments
Issue Links
- blocks
-
OAK-3716 Rewrite change on split
- Resolved
- is blocked by
-
OAK-5989 Create a partial index on _deletedOnce instead of sparse index
- Closed
-
OAK-6129 Create compound index on _sdType and _sdMaxRevTime
- Closed
- is related to
-
OAK-6161 Continuous flag for revisions collect command
- Closed
-
OAK-6719 add ability to run benchmarks with continuous version GC enabled (RDB fixtures)
- Closed
-
OAK-6859 Schedule Revision GC in DocumentNodeStoreService
- Closed
- relates to
-
OAK-3070 Use a lower bound in VersionGC query to avoid checking unmodified once deleted docs
- Closed
-
OAK-6536 Periodic log message from continuous RGC
- Closed