Project

General

Profile

Actions

Subtask #4306

closed

Feature #2149: osd: use omap for snap collections

make the new snap trimmer design work with split

Added by Samuel Just about 11 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
% Done:

90%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Short of a primitive to cheaply move extents of keys from object a to object b we will have to live with lazily cleaning up the snap collection mapping on the parents and children during future trims.
1) add support to SnapMapper for an hobject mask
2) add support to SnapMapper for invisibly removing filtered objects

Split will simply clone the snap mapping object off into the child objects and apply
more constrictive masks to the parent and child maps. Clone is copy on write as
well, so this operation should be bounded time not unduly hold up the split transaction.

Actions #1

Updated by Samuel Just about 11 years ago

  • % Done changed from 0 to 90
Actions #2

Updated by Loïc Dachary over 9 years ago

  • Status changed from New to Resolved
  • Translation missing: en.field_remaining_hours set to 0.0
Actions

Also available in: Atom PDF