Upgrade fails 2025.2.4 => 2025.4.0 (not enough time to complete migration of session to database) - Solved by removing redis sessions #14536
francescor
started this conversation in
General
Replies: 1 comment 1 reply
-
Yeah that migration can take quite a bit of time if you have many sessions. Deleting those sessions or temporarily removing the healthchecks are both valid workarounds. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
We've just upgraded from
2025.2.4 => 2025.4.0
In our docker swarm setup services "worker" and "server" where not able to finish the "Migrating Redis sessions to database" (reached 70% then the container was killed), so upgrade fails.
We still do not understand what was killing those services (we do not have healthchecks on those services), apparently 2 minutes after start.
We solved by cleaning up Redis sessions with this command
it was a quick and dirty fix we needed (users where waiting --- maintenance windows was over), not sure if it's a proper solution, but we could go on
Beta Was this translation helpful? Give feedback.
All reactions