Details
-
Epic
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
SegmentMK revision GC
Description
This is a container issue for the ongoing effort to improve revision gc of the SegmentMK.
I'm exploring
- ways to make the reference graph as exact as possible and necessary: it should not contain segments that are not referenceable any more and but must contain all segments that are referenceable.
- ways to segregate the reference graph reducing dependencies between certain set of segments as much as possible.
- Reducing the number of in memory references and their impact on gc as much as possible.
Attachments
Attachments
Issue Links
- is related to
-
OAK-4054 FileStore.containsSegment returns alway true (almost)
- Resolved
-
OAK-2498 Root record references provide too little context for parsing a segment
- Resolved
-
OAK-4011 Set online compaction default to paused
- Closed
-
OAK-4255 CLONE - FileStore.containsSegment returns alway true (almost)
- Closed
-
OAK-3485 FileStoreIT cleanup after tests
- Closed
- relates to
-
OAK-3481 CompactionMapTest does not close file store
- Closed
-
OAK-3315 SegmentMk shouldn't store binary segments in the cache
- Resolved
-
OAK-3309 Segment Tar SegmentCache loader stats
- Closed
-
OAK-3797 SegmentTracker#collectBlobReferences should retain fewer SegmentId instances
- Closed
-
OAK-2408 Investigate ways to make revision gc more precise
- Resolved