Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Reset CDS Profile fetch counters + Introduce generic PeriodTaskExecutor #901
Reset CDS Profile fetch counters + Introduce generic PeriodTaskExecutor #901
Changes from 4 commits
916f9de
759e091
471152e
0ba6ace
e2244f5
ca6b2c7
2c5bc23
443a8c7
f0ab4b8
59099b5
e2f8fef
4780bae
5344697
5edc16a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@dhaval24 I wonder if we need an additional executor for purging the cache. If
fetchProfile
is used frequently, you could store the last time it was called and purge the cache after elapsed time is over the threshold.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.
@littleaj there is a slight confusion due to naming. This should more be resetInterval. I have pushed the changes. I do not purge cache and that is not needed. We only reset the counter. If cache part of
InstrumentationKeyResolver
already has the appId resolved there is no need to retry.Regarding your comment on do we need additional service here. I would prefer to have seperate service as it adds clean seperation of what task is designated to which service.