Skip to content

Conversation

@ashishrp-aws
Copy link
Contributor

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Description

We have seen rise of the ExportResultArchive API failures to 15 per week, with retryable error messages.

ExportResultsArchiveError: Unable to execute HTTP request: The connection was closed during the request. The request will usually succeed on a retry, but if it does not: consider disabling any proxies you have configured, enabling debug logging, or performing a TCP dump to identify the root cause. If this is a streaming operation, validate that data is being read or written in a timely manner.

Adding backoff and retry to mitigate these errors.

Checklist

  • My code follows the code style of this project
  • I have added tests to cover my changes
  • A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
  • I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ashishrp-aws ashishrp-aws requested a review from a team as a code owner February 3, 2025 22:03
@ashishrp-aws ashishrp-aws requested a review from a team as a code owner February 3, 2025 22:54
return byteBufferList
}

/**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: If possible we can move this to a shared place.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Felt it was alright to keep it here in AmazonQStreamingClient class. Assuming that any other streaming APIs will be added here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@ashishrp-aws ashishrp-aws Feb 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this streaming API is a suspend function. tried using a common function for both but way to many conflicts

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can have a thin wrapper for the non-suspending use case instead of duplicating the logic

@ashishrp-aws ashishrp-aws enabled auto-merge (squash) February 4, 2025 19:11
@rli rli disabled auto-merge February 4, 2025 20:44
@ashishrp-aws ashishrp-aws enabled auto-merge (squash) February 5, 2025 00:07
@ashishrp-aws ashishrp-aws merged commit ac43387 into aws:main Feb 5, 2025
10 of 11 checks passed
KevinDing1 pushed a commit to KevinDing1/aws-toolkit-jetbrains that referenced this pull request Feb 6, 2025
…aming API. (aws#5320)

* Adding backoff and retry for export result archive.
@ashishrp-aws ashishrp-aws deleted the export branch February 10, 2025 20:09
gandhi-21 pushed a commit to gandhi-21/aws-toolkit-jetbrains that referenced this pull request Feb 26, 2025
…aming API. (aws#5320)

* Adding backoff and retry for export result archive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants