-
Notifications
You must be signed in to change notification settings - Fork 117
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
Data race using the default localized sampling strategy #164
Comments
Hi @jonaslu, Thanks for opening this issue. I tried to reproduce this but I did not see logs like this. Follow up questions from my side.
|
Hi, Hey (https://github.com/rakyll/hey) is a load-tester (you can use any load-tester - it's just to have some traffic om the server to invoke the race-condition). I'm running it in a terminal after starting the x-rayed server ( I know too little about the surroundings to fix it, but it happens here (when falling back to the localized sample strategy): I'm guessing the access to the |
Hi @jonaslu, Thanks for pointing out this issue. I was able to reproduce those data race warnings. I will add this item in our backlog for reference and will address this issue. |
Pushed out a fix for this issue (#196) |
I am closing this issue since we have pushed out a fix for this issue in this release (https://github.com/aws/aws-xray-sdk-go/releases/tag/v1.0.0-rc.15). Feel free to open another issue. |
Go xray version: v1.0.0-rc.14
Go version: go version go1.13.5 linux/amd64
Create a minimal http-server (copy paste the http-handler in the README.md)
Start the server with
go run -race main.go
and no xray-daemon running locally (will revert to localized strategy according to the docs:https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-go-configuration.html#xray-sdk-go-configuration-sampling)
Hit the server with some load (e g using hey):
hey -z 30s http://localhost:8000
This appears quite often in the logs:
The text was updated successfully, but these errors were encountered: