-
Notifications
You must be signed in to change notification settings - Fork 209
Open
Labels
C-bugCategory: This is a bugCategory: This is a bugE-easyEffort: Should be easy to implement and would make a good first PREffort: Should be easy to implement and would make a good first PR
Description
According to https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cloudfront-limits.html#limits-invalidations:
File invalidation: maximum number of active wildcard invalidations allowed
15
So, during times of heavy building (particularly when many crates in a family are released at once), we are likely to hit this limit. Presumably it will depend on how long the invalidations actually take.
We should decide what to do about these:
- queue the invalidations
- drop them when we hit the limit
- try to cluster same-prefixed crates that are built at once into a single invalidation
- if we hit the limit, set a ten-minute timer (to capture additional clustered builds), and invalidate the whole distribution when the timer expires
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bugCategory: This is a bugE-easyEffort: Should be easy to implement and would make a good first PREffort: Should be easy to implement and would make a good first PR