You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if the ingestor function take a long time to run (due to an error in the pipeline) there is no limit on the number of concurrent executions, mean the function can scale up and cost a lot.
Configuring a reserved concurrency limit in the CDK configuration should solve this. Currently the function hovers around 30-40 concurrent executions so limiting to 100 would provide a safe ceiling.
The text was updated successfully, but these errors were encountered:
Currently if the ingestor function take a long time to run (due to an error in the pipeline) there is no limit on the number of concurrent executions, mean the function can scale up and cost a lot.
Configuring a reserved concurrency limit in the CDK configuration should solve this. Currently the function hovers around 30-40 concurrent executions so limiting to 100 would provide a safe ceiling.
The text was updated successfully, but these errors were encountered: