Evgenii Stratonikov b5bcf90fa1 [#1186] engine: Read object directly from blobstor in case of conflicts ... 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 69e1e6ca20) Signed-off-by: Alex Vanin <alexey@nspcc.ru>		2022-03-28 13:48:44 +03:00
..
blobovnicza	[#1094] blobovnicza: calculate size in Init properly	2022-01-31 12:36:40 +03:00
blobstor	[#1085] blobstor: allow to ignore errors during iteration	2022-01-26 15:28:13 +03:00
engine	[#1186] engine: Read object directly from blobstor in case of conflicts	2022-03-28 13:48:44 +03:00
internal/log	[#790] storage engine: Add common template of log messages	2021-09-13 15:02:13 +03:00
metabase	[#1188] metabase: log PUT / DELETE operations	2022-03-28 13:48:44 +03:00
shard	[#1186] engine: Read object directly from blobstor in case of conflicts	2022-03-28 13:48:44 +03:00
util	*: replace neofs-api-go with neofs-sdk-go	2021-11-12 17:29:09 +03:00
writecache	[#1085] writecache: allow to ignore errors during iteration	2022-01-26 15:28:13 +03:00