frostfs-node

History

Evgenii Stratonikov c6af4a3ec8 All checks were successful DCO action / DCO (pull_request) Successful in 1m43s Details Vulncheck / Vulncheck (pull_request) Successful in 2m0s Details Tests and linters / Staticcheck (pull_request) Successful in 2m54s Details Build / Build Components (1.20) (pull_request) Successful in 2m49s Details Build / Build Components (1.21) (pull_request) Successful in 2m44s Details Tests and linters / Tests (1.21) (pull_request) Successful in 3m43s Details Tests and linters / Lint (pull_request) Successful in 3m58s Details Tests and linters / Tests (1.20) (pull_request) Successful in 23m28s Details Tests and linters / Tests with -race (pull_request) Successful in 29m0s Details [#679 ] engine: Do not increase error counter on meta mismatch It was introduced in `69e1e6ca` to help node determine faulty shards. However, the situation is possible in a real-life scenario: 1. Object O is evacuated from shard A to B. 2. Shard A is unmounted because of lower-level errors. 3. We now have object in meta on A and in blobstor on B. Technically we have it in meta on shard B too, but we still got the error if B goes to a degraded mode. Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>		2023-09-14 10:39:18 +03:00
..
logs	[#679 ] engine: Do not increase error counter on meta mismatch	2023-09-14 10:39:18 +03:00