DCO action / DCO (pull_request) Successful in 1m43sDetails
Vulncheck / Vulncheck (pull_request) Successful in 2m0sDetails
Tests and linters / Staticcheck (pull_request) Successful in 2m54sDetails
Build / Build Components (1.20) (pull_request) Successful in 2m49sDetails
Build / Build Components (1.21) (pull_request) Successful in 2m44sDetails
Tests and linters / Tests (1.21) (pull_request) Successful in 3m43sDetails
Tests and linters / Lint (pull_request) Successful in 3m58sDetails
Tests and linters / Tests (1.20) (pull_request) Successful in 23m28sDetails
Tests and linters / Tests with -race (pull_request) Successful in 29m0sDetails
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>
We never propagate delete requests to the container node, because
tombstone broadcast is done via PUT. No need to pollute logs.
Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
Vulncheck / Vulncheck (pull_request) Successful in 2m37sDetails
Build / Build Components (1.21) (pull_request) Successful in 3m36sDetails
Tests and linters / Staticcheck (pull_request) Successful in 3m36sDetails
DCO action / DCO (pull_request) Successful in 4m16sDetails
Tests and linters / Lint (pull_request) Successful in 5m34sDetails
Tests and linters / Tests (1.20) (pull_request) Successful in 5m36sDetails
Tests and linters / Tests (1.21) (pull_request) Successful in 5m46sDetails
Tests and linters / Tests with -race (pull_request) Successful in 6m21sDetails
Build / Build Components (1.20) (pull_request) Successful in 8m1sDetails
* Use DeletionInfo method from morph client to check if
the container has been really removed from neo-go
Signed-off-by: Airat Arifullin a.arifullin@yadro.com
ci/woodpecker/push/pre-commit Pipeline was successfulDetails
Current implementation has some quirks. For example,
using only half of object.put.pool_size_remote threads
tells replicator that is node is 50% loaded,
but in reality we could be putting lot's of big objects.
Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com>
Now it's possible to run evacuate shard in async.
Also only one evacuate process can be in progress.
Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com>
It's not really needed, closing the connection works fine when exiting and
normally the app doesn't need to unsubscribe at all.
Signed-off-by: Roman Khimov <roman@nspcc.ru>
Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
Evgenii Stratonikov
Anton Nikiforov
Dmitrii Stepanov
Airat Arifullin
Alexander Chuprov
Alejandro Lopez
Roman Khimov
Pavel Karpy