From a24f582ff50bf5cfc4b52dd3f2cf9e1973d43593 Mon Sep 17 00:00:00 2001 From: Jamil Date: Fri, 27 Jun 2025 13:58:58 -0700 Subject: [PATCH] fix(portal): increase change_log lag warning threshold (#9702) This is needlessly short and has already tripped a false alarm once. --- .../domain/lib/domain/change_logs/replication_connection.ex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/elixir/apps/domain/lib/domain/change_logs/replication_connection.ex b/elixir/apps/domain/lib/domain/change_logs/replication_connection.ex index 687f0b7ad..920024402 100644 --- a/elixir/apps/domain/lib/domain/change_logs/replication_connection.ex +++ b/elixir/apps/domain/lib/domain/change_logs/replication_connection.ex @@ -2,9 +2,9 @@ defmodule Domain.ChangeLogs.ReplicationConnection do alias Domain.ChangeLogs use Domain.Replication.Connection, - # Allow up to 30 seconds of processing lag before alerting - this should be less - # than or equal to the wal_sender_timeout setting, which is typically 60s. - warning_threshold_ms: 30 * 1_000, + # Allow up to 5 minutes of processing lag before alerting. This needs to be able to survive + # deploys without alerting. + warning_threshold_ms: 5 * 60 * 1_000, # 1 month in ms - we never want to bypass changelog inserts error_threshold_ms: 30 * 24 * 60 * 60 * 1_000