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
..
core	[#1100] *: Adopt new SDK's owner.ID API	2022-01-21 17:58:30 +03:00
innerring	[#1180] ir/internal: Fix audit range hash type	2022-03-28 13:03:12 +03:00
local_object_storage	[#1186] engine: Read object directly from blobstor in case of conflicts	2022-03-28 13:48:44 +03:00
metrics	[#1054] neofs-node: add epoch metric	2021-12-28 15:34:20 +03:00
morph	[#1023] *: fix linter errors	2022-01-31 13:01:58 +03:00
network	[#1087] *: Adopt SDK changes	2022-01-14 17:29:03 +03:00
services	[#1023] services/object: remove TTL from Get parameters	2022-01-31 13:01:58 +03:00
util	[#851] util/rand: use single random source	2022-01-12 19:29:27 +03:00