forked from TrueCloudLab/frostfs-node
Aleksey Savchuk
432042c534
Currently, it's allowed to inhume or lock an expired object. Consider the following scenario: 1) An user inhumes or locks an object 2) The object expires 3) GC hasn't yet deleted the object 4) The node loses the associated tombstone or lock 5) Another node replicates tombstone or lock to the first node In this case, the second node succeeds, which is the desired behavior. Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com> |
||
|---|---|---|
| .. | ||
| blobovnicza | ||
| blobstor | ||
| engine | ||
| internal | ||
| metabase | ||
| metrics | ||
| pilorama | ||
| shard | ||
| util | ||
| writecache | ||