From 76daa237402f3e271a19bd9a4369ae04b7ac0def Mon Sep 17 00:00:00 2001 From: steffen911 Date: Tue, 17 Dec 2024 08:38:16 +0100 Subject: [PATCH] chore: add note on zero-donwtime background migrations --- next-env.d.ts | 3 +-- pages/self-hosting/upgrade-guides/upgrade-v2-to-v3.mdx | 7 +++++++ 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/next-env.d.ts b/next-env.d.ts index 3cd7048ed..a4a7b3f5c 100644 --- a/next-env.d.ts +++ b/next-env.d.ts @@ -1,6 +1,5 @@ /// /// -/// // NOTE: This file should not be edited -// see https://nextjs.org/docs/app/api-reference/config/typescript for more information. +// see https://nextjs.org/docs/pages/building-your-application/configuring/typescript for more information. diff --git a/pages/self-hosting/upgrade-guides/upgrade-v2-to-v3.mdx b/pages/self-hosting/upgrade-guides/upgrade-v2-to-v3.mdx index 1f7d4243e..907ec32c5 100644 --- a/pages/self-hosting/upgrade-guides/upgrade-v2-to-v3.mdx +++ b/pages/self-hosting/upgrade-guides/upgrade-v2-to-v3.mdx @@ -180,6 +180,13 @@ Also, ensure that you run a recent version of Langfuse, ideally a version later For a zero-downtime upgrade, we recommend that you provision new instances of the Langfuse web and worker containers and move your traffic after validating that the new instances are working as expected. + + If you go for the zero-downtime upgrade, we recommend to disable background migrations until you shift traffic to the new instances. + Otherwise, the migration may miss events that are ingested after the new instances were started. + Set `LANGFUSE_ENABLE_BACKGROUND_MIGRATIONS=false` in the environment variables of the new Langfuse web and worker containers until traffic is shifted. + Afterwards, remove the overwrite or set to `true`. + + ### Upgrade Steps