[#355] Increase tree svc client cache size to test hypotheses #358
No reviewers
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#358
Loading…
Reference in a new issue
No description provided.
Delete branch "ale64bit/frostfs-node:fix/355-increase-tree-service-client-cache-size"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Signed-off-by: Alejandro Lopez a.lopez@yadro.com
It's possible that after a certain number of nodes, the cache starts thrashing due to closing connections on eviction. While this PR doesn't solve the problem per se, it's useful to test the hypotheses.
Ultimately, the solution is probably to move away from using a bounded cache (even a configurable value would be prone to thrashing if used incorrectly) and have a better mechanism to detect when certain addresses go out of scope in order to close the corresponding connections. Also, we shouldn't be using
WithBlock
and instead we should leverage existing backoff and keepalive options to accomplish the same whenever possible.Can you make this PR for support branch too?
support/v0.36