forked from TrueCloudLab/frostfs-node
dbbbef9ddb
Previously, node could get an "infinite" small object: it could be expired and thus could not be flushed (update its storage ID) to metabase => could not be marked as flushed => node never removes such object and repeat all the cycle one more time. If object exists and is not marked with GC (meta returns `ErrObjectIsExpired`, not `ObjectNotFound` and not `ObjectAlreadyRemoved`), its ID is safe to update _in the same_ bbolt transaction. Signed-off-by: Pavel Karpy <p.karpy@yadro.com> |
||
|---|---|---|
| .. | ||
| core | ||
| innerring | ||
| local_object_storage | ||
| metrics | ||
| morph | ||
| network | ||
| services | ||
| util | ||