[Usage Collection] Reuse concurrent collectors #151626
Merged
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.
Summary
This is part of our attempts to reduce the impact of Usage Collection in Kibana: This PR reuses the promise of an ongoing collector in case of a subsequent call comes in.
This is an extra layer of protection to the current
refreshCache: false
behavior. In some cases, we've seen explicitrefreshCache: true
calls that may overload Kibana if an expensive Usage Collector takes longer to process, and a new request comes in.For maintainers