I want to configure the retain.concurrency:1 parameter to reduce disk load during garbage collection. What negative consequences can this have?
Non. I am running it like this all the time. My question is more the other way around. Why don’t we make 1 concurrent retain the new default?
7 Likes
what does this command do and why do you need it?
1 Like
What is the default if this parameter is not set?
storagenode run --help will print out all default values
3 Likes
What is the behaviour when the number of retain requests (i.e. bloom filters received) exceeds the retain.concurrency value? Does it reject the request, accept and queue the request, cancel the current retain process and start the received request or other?
pmw6tvzmf2jv6giyybmmvl4o2ahqlaldsaeha4yx74n5aaaaaaaa-1716130689348472000
qstuylguhrn2ozjv4h2c6xpxykd622gtgurhql2k7k75wqaaaaaa-1716141599172348000
ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa-1715795999994095000
ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa-1715968799997895000
v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa-1716141599968771000
BFs are stored and worked through one by one (or whatever your retain is).
2 Likes