From 50496037ace69b2fec8191ccbd4cd35307de98b5 Mon Sep 17 00:00:00 2001 From: Preslav Le Date: Wed, 13 Mar 2024 11:39:43 -0700 Subject: [PATCH] Reduce AWS Lambda deploy splay. (#23330) The purpose of this limit was to splay updates to avoid overloading AWS control plane API. However, adding a splay so large, started adding confusion since it takes 30 minutes between deploying backend and changes to the AWS Lambda code taking effect. The long term correct solution is to have a global rate limiter that rate limits AWS Lambda Control Plan updates. Lower the splay as a stop gap measure. GitOrigin-RevId: 87ddab1a12215064cd491ad521ea66c5106d54f9 --- crates/common/src/knobs.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/common/src/knobs.rs b/crates/common/src/knobs.rs index 61b8a406..42aa5734 100644 --- a/crates/common/src/knobs.rs +++ b/crates/common/src/knobs.rs @@ -766,7 +766,7 @@ pub static BACKEND_ISOLATE_ACTIVE_THREADS_PERCENT: LazyLock = /// How long to splay deploying AWS Lambdas due to changes in the backend. This /// know doesn't delay deploys that are required due to user backends. pub static AWS_LAMBDA_DEPLOY_SPLAY_SECONDS: LazyLock = - LazyLock::new(|| Duration::from_secs(env_config("AWS_LAMBDA_DEPLOY_SPLAY_SECONDS", 1800))); + LazyLock::new(|| Duration::from_secs(env_config("AWS_LAMBDA_DEPLOY_SPLAY_SECONDS", 300))); /// The number of seconds backend should wait for requests to drain before /// shutting down after SIGINT.