Fix another race condition that causes lost metrics#137
Open
pwinckles wants to merge 2 commits intoperformancecopilot:mainfrom
Open
Fix another race condition that causes lost metrics#137pwinckles wants to merge 2 commits intoperformancecopilot:mainfrom
pwinckles wants to merge 2 commits intoperformancecopilot:mainfrom
Conversation
This fixes another race condition that causes metrics to be lost when they are updated while the writer is stopped and after the monitorable has been re-added to the writer. In this case, the update needs to set the initial value on `PcpValueInfo` so that the correct value is written when the writer is started.
Adds a cache to the `MetricNameMapper` and `MetricNameValidator`. This improves performance of mapping metric names because a regex no longer has to be executed over and over again. The validator cache helps because the metric name no longer has to be encoded over and over again. Neither of these caches expire entries, but this is not an issue because it's currently not possible to remove monitorables from Parfait.
Contributor
Author
|
Any thoughts on a path forward here? |
Member
|
@pwinckles it conceptually makes sense to me - I'm guessing retired life is treating @tallpsmith very well and we wont hear from him, so please go ahead and merge when you are happy with your PRs (I don't have the java experience to give you deep and meaningful reviews). |
Contributor
Currently a glorified kids Uber driver: ...and general house-wife. Not easy to find a chunk of time to sit and concentrate at the moment! :( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes another race condition that causes metrics to be lost when they are updated while the writer is stopped and after the monitorable has been re-added to the writer. In this case, the update needs to set the initial value on
PcpValueInfoso that the correct value is written when the writer is started.Additionally, while I was working on this, I noticed that if you have thousands of monitorables, then re-adding them in
PcpMonitorBridge.startMonitoring()can take a very long time. For example, on one system I was seeing it take >20 seconds to add 40k monitorables. To help alleviate this problem, I added a cache to the metric name mapper and validator.Resolves #132