-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Ensure that Cache options are reloaded when consul reload
is performed
#8552
Ensure that Cache options are reloaded when consul reload
is performed
#8552
Conversation
…med. This will apply cache throttling parameters are properly applied: * cache.EntryFetchMaxBurst * cache.EntryFetchRate When values are updated, a log is displayed in info.
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.
Thank you for the PR! This looks like an excellent addition. One suggestion inline, and a test case for reloading would be great.
A test case in agent/cache/cache_test.go
could create a cache, register a MockType
, create an entry with Get
, then call ReloadOptions
, and check that the limiter on the entry has the new values by calling Limit()
and Burst()
.
6ad861e
to
879d087
Compare
@dnephin All Done |
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.
LGTM!
🍒✅ Cherry pick of commit 72bf350 onto |
…onfig Ensure that Cache options are reloaded when `consul reload` is performed
Oh, I forgot we need to add a changelog entry for this! Hans has some example of how to do that here #8387 if you don't mind adding it. |
Added changelog for #8552
This will apply cache throttling parameters are properly applied:
When values are updated, a log is displayed in info.
This will help to mitigate #7863 when values need to be updated without any downtime of agents