Closed thorfi closed 2 years ago
bump
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it had not recent activity during the stale period.
Description
docker compose up
anddocker compose convert
fail due to AWS API throttling if there are over 100 EFS file systems.Also
docker compose up
fails due to AWS API throttling while waiting for the stack to complete on large stacks with a lot of resources as the number of describes goes over the thresholds.In both cases, AWS API documentation recommends using exponential backoff to allow the API call count bucket to refill, rather than just crashing.
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html#api-request-rate
( Re-raised from docker/compose#9177 )
Steps to reproduce the issue:
docker compose up
docker compose --verbose up
ordocker compose --verbose convert
Describe the results you received:
ThrottlingException: status code: 400, request id: 2259a3c2-1130-4034-a41f-24914d8fa550
Describe the results you expected:
docker compose up
- CloudFormation Stack should be createddocker compose convert
- CloudFormation .yaml code should be printedAdditional information you deem important (e.g. issue happens only occasionally):
This was not happening in
docker compose convert
previously, but now it is.docker compose up
has had the problem for a long time.Having done some digging with --verbose on:
if there are < 100 EFS entries everything works:
If there are >= 100 EFS ids it fails:
Related AWS Documentation:
Output of
docker compose version
:Output of
docker info
:Additional environment details:
macOS Monterey, MacBook Pro M1.