-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
fix(config): wire up Provider.Enabled
flag
#10804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Adds missing config option described in #10803
removing experiment, replaced with Provider.Enabled
2029418
to
f28bc86
Compare
updated and added tests for manually triggering provide and reprovide and making them respect global configuration flag to avoid inconsistent behaviors
Provider.Enable
flagProvider.Enabled
flag
Provider.Enabled
flagProvider.Enabled
flag
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering whether we actually want Reprovide.Interval=0
to disable the provide system altogether? (see comments)
- simplified default for both - 16 is safer for non-accelerated DHT client - acceletated DHT performs better without limit anyway - updated docs
Confirmed this PR (mainly, ability to disable provider queue) restores goroutine/memory utilization that is on par or better than v0.34.1 (internal notes from our staging env). Merging – will include this in 0.35.0-rc2. |
* fix(config): explicit Provider.Enabled flag Adds missing config option described in #10803 * refactor: remove Experimental.StrategicProviding removing experiment, replaced with Provider.Enabled * test(cli): routing [re]provide updated and added tests for manually triggering provide and reprovide and making them respect global configuration flag to avoid inconsistent behaviors * docs: improve DelegatedRouters * refactor: default DefaultProviderWorkerCount=16 - simplified default for both - 16 is safer for non-accelerated DHT client - acceletated DHT performs better without limit anyway - updated docs (cherry picked from commit 2ab3f58)
Kubo 0.35.0-rc1 had issues on Staging environment due too OOMs (internal notes).
@guillaumemichel and @gammazero suggested that the problem is related to provides, which should be disabled on that box. This PR aims to implement ability to fully disable provides (and reprovides) as noted in #10803 and unblock Kubo 0.35 (#10760)
TODO
Provider.Enabled
is a global flag for disabling both Provider and Reprovider systems (announcing new/old CIDs to amino DHT).Experimental.StrategicProviding
. Superseded byProvider.Enabled
,Reprovider.Interval
andReprovider.Strategy
.Provider.WorkerCount
when no Accelerated DHT clientrouting [re]provide
commands, ensure global flags are respectedProvider.WorkerCount