forked from TrueCloudLab/frostfs-node
d4569946c5
In previous implementation `Container.Delete` operation caused local node's cache invalidation (container itself, eACL and listings). Any subsequent `Container.Get` operation reversed invalidation. Given the low latency sensitivity of deleting a container, there is no need to touch the cache. With this approach, all pending deletion operations on the node via the NeoFS API protocol will be delayed by the cache TTL. Do not call cache invalidation ops in `morphContainerWriter.Delete`. Remove no longer needed `InvalidateContainerListByCID` and `InvalidateContainer` methods. Signed-off-by: Leonard Lyubich <leonard@nspcc.ru> |
||
|---|---|---|
| .. | ||
| config | ||
| reputation | ||
| accounting.go | ||
| attributes.go | ||
| cache.go | ||
| config.go | ||
| container.go | ||
| control.go | ||
| grpc.go | ||
| main.go | ||
| metrics.go | ||
| morph.go | ||
| netmap.go | ||
| notificator.go | ||
| object.go | ||
| pprof.go | ||
| reputation.go | ||
| session.go | ||
| timers.go | ||
| worker.go | ||