-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[internal/coreinternal/processor/filterset/regexp] LRU cache is not safe for concurrent access #11829
Comments
pinging @boostchicken @pmm-sumo as code owners of the filterprocessor |
@TylerHelmuth The problem seems to be |
I think we could switch to |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Bug is still present in Too bad the PR auto-closed! Interestingly, #16103: [chore] spanmetricsprocessor: switch to use non-thread safe lru, already protected by proc mu was merged the day before this very issue went stale: The |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I maintain an internal fork that uses hashicorp LRU to work around this bug. It would be great to have this fixed. |
We are working towards removing the |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Fixes #11829 Signed-off-by: Bogdan Drutu <[email protected]>
…ry#29869) Fixes open-telemetry#11829 Signed-off-by: Bogdan Drutu <[email protected]>
Describe the bug
The processor/filterprocessor with a regexp cache may happens to
fatal error: concurrent map read and map write
Steps to reproduce
Concurrent to filter metrics by filterprocessor with a regexp and a lru cache
What did you expect to see?
concurrent safe to use regexp filterset with a lru cache
What did you see instead?
What version did you use?
Version: v0.54.0
What config did you use?
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: