forked from TrueCloudLab/frostfs-node
b5bcf90fa1
Metabase is expected to contain actual information about objects stored
in shard. If the object is present in metabase but is missing from
blobstor, peform an additional attempt to fetch it directly without
consulting metabase. Such a situation is unexpected, so error counter
is increased for the shard which has the object in the metabase. We
don't increase error counter for the shard which has the object in
blobstor, because some garbage can be expected there. In this
implementation there is no overhead for objects which are really
missing, i.e. are not present in any metabase.
Signed-off-by: Evgenii Stratonikov <evgeniy@nspcc.ru>
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| container.go | ||
| control.go | ||
| control_test.go | ||
| delete.go | ||
| dump.go | ||
| engine.go | ||
| engine_test.go | ||
| error_test.go | ||
| exists.go | ||
| get.go | ||
| head.go | ||
| head_test.go | ||
| info.go | ||
| inhume.go | ||
| inhume_test.go | ||
| list.go | ||
| list_test.go | ||
| metrics.go | ||
| put.go | ||
| range.go | ||
| restore.go | ||
| select.go | ||
| shards.go | ||