-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Fix statsd concurrency bug #8885
Conversation
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.
🤝 ✅ CLA has been signed. Thank you!
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.
we're sure this is the cause, and not the cached changes?
edit: slacked you some thoughts
Updated to keep somewhat of the 'optimization' by adding the lock only to parseName. From my various tests, this works as well. |
!retry-checks |
4 similar comments
!retry-checks |
!retry-checks |
!retry-checks |
!retry-checks |
* Fix the issue * Remove test I was using for replication * Accidentally removed test. * Add lock only where it is necessary. * eliminate unnecessary space
This bug was inadvertently caused by a small optimization I attempted to make in a previous PR, simply resetting that change here.
Closes #8695