-
Notifications
You must be signed in to change notification settings - Fork 144
message too long errors #21
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
Comments
Hi, the SDK has thin layer modular design. The X-Ray recorder decides when to stream a segment (e.g. send out some closed children subsegments first) and the emitter simply executes what it is told to do. The default maximum number of subsegments it holds is set to 30: https://github.com/aws/aws-xray-sdk-python/blob/master/aws_xray_sdk/core/recorder.py#L46. The reason of using size of a subsegments array is that byte counting is expensive. Depends on what do your segment look like 30 subsegments could still be large. You can modify it to a lower value so the streaming happens earlier and more frequent. This number is tested under UDP packet size 64KB but depend on your operating system configuration it might allow an even smaller packet pass through. Hope it helps. |
Close. Feel free to re-open for any additional comment. |
I believe this is not configurable in xray-sdk, is this not the case? See https://github.com/aws/aws-xray-sdk-python/blob/master/aws_xray_sdk/core/recorder.py#L46 |
unfortunately I'm not allowed to re-open |
Sorry about that. You are right. I confused it with our another SDK. The public interface For workaround you can temporarily use |
Released as part of 0.96. |
Just for record: looks like in current version
Also it is exposed as |
Occasionally I'll get the following error from the udp_emitter:
my guess is that there's too much data in the trace. This sounds like a library problem, if there's too much data it should split it into multiple packets.
The text was updated successfully, but these errors were encountered: