Invalidate list cache on container events #802

Merged
fyrchik merged 4 commits from fyrchik/frostfs-node:remove-invalidate-cache into master 2023-11-14 19:00:13 +00:00

4 commits

Author SHA1 Message Date
6fc0d791d1 [#506] node: Invalidate list cache after container add/removal
All checks were successful
DCO action / DCO (pull_request) Successful in 1m32s
Build / Build Components (1.21) (pull_request) Successful in 3m54s
Vulncheck / Vulncheck (pull_request) Successful in 3m31s
Build / Build Components (1.20) (pull_request) Successful in 4m14s
Tests and linters / Staticcheck (pull_request) Successful in 5m18s
Tests and linters / Lint (pull_request) Successful in 5m54s
Tests and linters / Tests (1.21) (pull_request) Successful in 6m55s
Tests and linters / Tests (1.20) (pull_request) Successful in 7m7s
Tests and linters / Tests with -race (pull_request) Successful in 7m14s
`update` already has problems mentioned in its doc-comment and the code
itself is not straightforward. Invalidating cache altogether seems like
a better option because we don't construct cache output ourselves (thus, no
"impossible" results).

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
2023-11-14 14:48:27 +03:00
3f61b3a677 [#506] node: Use DeletionInfo() method to get deleted container owner
Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
2023-11-14 14:48:27 +03:00
72933e2d53 [#506] container: Use uint64 for epoch type
It is `uint64` in netmap source interfaces and other code.

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
2023-11-14 14:48:27 +03:00
5f01dffd45 [#506] container: Use user.ID in DeletionInfo response
Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
2023-11-14 14:41:13 +03:00