Dmitrii Stepanov
f2437f7ae9
All checks were successful
DCO action / DCO (pull_request) Successful in 1m36s
Build / Build Components (1.20) (pull_request) Successful in 3m46s
Vulncheck / Vulncheck (pull_request) Successful in 3m16s
Tests and linters / Staticcheck (pull_request) Successful in 4m42s
Tests and linters / Tests (1.20) (pull_request) Successful in 6m27s
Tests and linters / Tests (1.21) (pull_request) Successful in 6m35s
Tests and linters / Tests with -race (pull_request) Successful in 6m33s
Build / Build Components (1.21) (pull_request) Successful in 13m7s
Tests and linters / Lint (pull_request) Successful in 19m14s
Due to the flushing data from the writecache to the storage and simultaneous deletion, a partial deletion situation is possible. So as a solution, deletion is allowed only when the object is in storage, because object will be deleted from writecache by flush goroutine. Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com> |
||
---|---|---|
.. | ||
mode | ||
container.go | ||
control.go | ||
control_test.go | ||
count.go | ||
delete.go | ||
delete_test.go | ||
errors.go | ||
exists.go | ||
gc.go | ||
gc_internal_test.go | ||
gc_test.go | ||
get.go | ||
get_test.go | ||
head.go | ||
head_test.go | ||
id.go | ||
info.go | ||
inhume.go | ||
inhume_test.go | ||
list.go | ||
list_test.go | ||
lock.go | ||
lock_test.go | ||
metrics_test.go | ||
mode.go | ||
move.go | ||
put.go | ||
range.go | ||
range_test.go | ||
reload_test.go | ||
select.go | ||
shard.go | ||
shard_test.go | ||
shutdown_test.go | ||
tree.go | ||
weight.go | ||
writecache.go |