Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
Changes that are committed during a segment store compaction run will be compacted on top of the already compacted changes. However the compactor uses the wrong before state in this case. Instead of compacting against the compacted before state it uses the un-compacted before state. The resulting state will thus contain references to un-compacted state, making those not eligible for later clean up.
Attachments
Attachments
Issue Links
- depends upon
-
OAK-2140 Segment Compactor will not compact binaries > 16k
- Closed
-
OAK-2254 Observation events accessibility check should respect session refresh settings
- Closed
-
OAK-2255 PermissionStoreImpl refresh root on flush
- Closed
-
OAK-2256 MemoryNodeBuilder NPE on base() following root refresh
- Closed
-
OAK-2259 SegmentBlob equals check should verify compaction in both directions
- Closed
- is depended upon by
-
OAK-2045 Long running JCR session prevent live cleanup in Segment FileStore
- Resolved
- is related to
-
OAK-2045 Long running JCR session prevent live cleanup in Segment FileStore
- Resolved
-
OAK-2271 Compaction estimation time should not depend on number of checkpoints
- Closed
- relates to
-
OAK-2322 Compaction estimation includes all data segments
- Closed
-
OAK-2449 offline compaction (via oak-run) broken
- Closed