-
Notifications
You must be signed in to change notification settings - Fork 714
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
Multithreading issue in ZipkinSpanCollector #60
Comments
Any thoughts on the same? |
Hi, Feel free to submit a pull request. I might do a request to ask if it would be feasible to remove the support for multiple threads here #59. |
Hi @kristofa Thanks for your reply. I guess you are right, we might not need to have more than a thread if the sampling rate is correct but as a part of performance testing we might need to use more than a thread to throttle the system. Let me make a fix for this and will send the pull request. |
Hi @kristofa , I have submitted the pull request for the issue : #64 Please have a look and let me know in case there is any issue with the change. Would it also be possible for you to release it, so that instead of using the patch in our production, we can use your library directly. Thanks, |
I had 1 small remark on the pr. Once that's in place I can merge it. |
Hi @kristofa, I have fixed the code according to your comment. Please have a look. We have been using with single thread and its working perfectly. But as I said earlier, at the time of QA regression and load testing, when we are passing nrOfThreads > 1, it is failing. It would be nice, if you can release, otherwise we would patch the code. No issues 👍 |
Hi @kristofa, Could you please check the pull request and merge the code? Thanks |
Hi @kristofa, Could you please check the pull request and merge the code? Thanks |
I merged the pr. It will end up in a release which will be available hopefully by Monday. |
@kristofa Thanks 👍 |
Hi,
I could see that if in ZipkinSpanCollector, if you have more that one SpanProcessingThread, all the threads are sharing the same instance of ZipkinCollectorClientProvider. Hence there is a serious multithreading issue.
The text was updated successfully, but these errors were encountered: