-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
remove locking from jaeger receiver start and stop processes #3070
remove locking from jaeger receiver start and stop processes #3070
Conversation
@bhautikpip have you confirmed that this is not needed? |
@bogdandrutu I have not tested this changes with multiple requests to see wether we would be requiring locks or not. I kinda followed the issue description. Any recommendation on best way to test this? |
I think the field |
Ran |
…lemetry#3070) * remove locking from jaeger receiver start and stop processes * remove mutex field
…lemetry#3070) * remove locking from jaeger receiver start and stop processes * remove mutex field
Description: <Describe what has changed.
Remove locking from start and stop functions - jaeger receiver
Link to tracking Issue:
#3041
Testing: < Describe what testing was performed and which tests were added.>
Documentation: < Describe the documentation added.>
Please delete paragraphs that you did not use before submitting.