-
Notifications
You must be signed in to change notification settings - Fork 858
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
SegmentNotFoundException when using S3 TransferManager to multiPart upload files, tracing by AWS XRay #3217
Comments
Hi @Zhenye-Na thank you for reaching out. We got the same issue reported but for X-Ray and the SDK client-side metrics here: #2919. As it's mentioned in the comments, it's not something we can fix on the SDK side without X-Ray support. We've opened an issue in the X-Ray SDK repo and we're tracking progress over there: aws/aws-xray-sdk-java#330. Let us know if this helps. |
Thanks, I subscribed the issue you created. Let's see what X-Ray team replies and how to sort this out. |
Hi @Zhenye-Na, I'll go ahead and close this issue since we cannot move forward in the SDK without the support from the X-Ray team. |
|
Describe the bug
Existing rasied issues:
Basically the problem is that
transferManager
manages its own thread pool and XRay is not able to gather context for the threads thattransferManager
created. In this case,SegmentNotFoundException
has been raisedExpected Behavior
TransferManager should be compatible with XRay for request tracing
Current Behavior
SegmentNotFoundException
is raisedReproduction Steps
S3 Multipart Upload High Level API - https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpu-upload-object.html
and on top of this, using XRay to trace the request
Possible Solution
No response
Additional Information/Context
No response
AWS Java SDK version used
AWSS3JavaClient = 1.12.x
JDK version used
JDK 8
Operating System and version
Amazon Linux 2
The text was updated successfully, but these errors were encountered: