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
Copy file name to clipboardExpand all lines: docs/content/en/open_source/upgrading/2.52.md
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,4 +9,25 @@ Since the license change at Redis the fork ValKey has become widely popular and
9
9
10
10
Defect Dojo 2.52 now uses ValKey as a message broker. Teh existing redit volume can be used by Valkey, so this is just a drop in replacement.
11
11
12
-
If you want to know more or have a setup where you cannot just re-use the existing volume, please visit https://valkey.io/topics/migration/.
12
+
If you want to know more or have a setup where you cannot just re-use the existing volume, please visit https://valkey.io/topics/migration/.
13
+
14
+
When you shutdown Defect Dojo to perform the upgrade, the celery tasks that are in the queue are storede to disk. After the upgrade, the celery workers will process these tasks as normal.
15
+
16
+
If you want to be 110% sure no tasks will be lost you could perform the upgrade in two steps:
17
+
18
+
1) Stop nginx, uwsgi, celerybeat to prevent new tasks from being created:
19
+
20
+
`docker compose down nginx, uwsgi, celerybeat`
21
+
22
+
2) Observe the logs of the celeryworker(s) and wait until all tasks are finished:
23
+
24
+
`docker compose logs celeryworker`
25
+
26
+
3) Stop the remaining services:
27
+
28
+
`docker compose down`
29
+
30
+
4) Continue the upgrade as normal per the [upgrade guide](upgrading_guide)
0 commit comments