node: Move gc from Shard level to StorageEngine #1151

Open
opened 2024-05-30 06:47:53 +00:00 by acid-ant · 0 comments
Collaborator

Currently, LOCK object, sign in metabase about lock and locked object can be placed on separate shards.
This leading to race between policer and gc.

To solve this for EC object the exist method returns lock marker, this forces lock action when we put reconstructed chunk.
The same is valid for regular objects when policer recovering copy.

In scope of this task, need to consider the option of moving gc form Shard to StorageEngine level.

Currently, LOCK object, sign in metabase about lock and locked object can be placed on separate shards. This leading to race between `policer` and `gc`. To solve this for EC object the `exist` method returns lock marker, this forces lock action when we `put` reconstructed chunk. The same is valid for regular objects when `policer` recovering copy. In scope of this task, need to consider the option of moving `gc` form `Shard` to `StorageEngine` level.
acid-ant added the
triage
label 2024-05-30 06:47:53 +00:00
fyrchik added this to the vNext milestone 2024-06-20 11:31:35 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-node#1151
There is no content yet.