forked from TrueCloudLab/frostfs-node
Aleksey Savchuk
3f4df881c9
Currently, when an object on some shard is inhumed, the engine places a tombstone on the same shard. If the target shard is read-only, the engine fails. In that case, we want the engine to correctly place a tombstone on a different shard, ensuring that: - An object becomes unavailable if a tombstone was placed on a different shard. See `TestObjectUnavailableIfTombstoneOnDifferentShard` test. - GC deletes an object if a tombstone was placed on a different shard. See `TestObjectDeletedIfTombstoneOnDifferentShard` test. Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com> |
||
---|---|---|
.. | ||
blobovnicza | ||
blobstor | ||
engine | ||
internal | ||
metabase | ||
metrics | ||
pilorama | ||
shard | ||
util | ||
writecache |