Versions Compared

Old Version 3

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

compared with

New Version Current

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Renamed page and marked excerpt.

Excerpt

The AWS API is eventually consistent only and also exhibits a customer specific dynamic throttling policy, both of which require respective retry logic to be in place. Accordingly the facilitated AWS SDK for Java features an exponential backoff strategy already, but its default retry number of 3 (accumulating to a retry window of up to ~4 seconds) has proven to be too low for the

tasks

use case at hand

and has been increased to 7 accordingly

. The values are configurable accordingly, with an increased default retry number of 7 (accumulating to a retry window of up to ~1 minute).

This The increased defaults should ideally be sufficient for most scenarios, but the values are adjustable can be adjusted by defining one or both of the following variables if need be:

  • bamboo.custom.aws.maxErrorRetry - how many retries should the exponential backoff algorithm perform (default: 7)
  • bamboo.custom.aws.awaitTransitionInterval - how long should the task wait before querying the resource transition state again (default: 15000 milliseconds)