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
Fail in-progress jobs when the worker running them exits abnormally
This applies to:
- Killed workers that the supervisor detects as dead.
- Reaped workers without a clear exit status.
- Orphaned executions that somehow lost their worker.
- Workers whose heartbeat expired.
Copy file name to clipboardExpand all lines: UPGRADING.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,28 @@
1
+
# Upgrading to version 0.6.x
2
+
3
+
## New migration in 3 steps
4
+
This version adds a new migration to the `solid_queue_processes` table. This migration adds a new column that needs to be `NOT NULL`. It will run in three steps:
5
+
1. Add the new column, nullable
6
+
2. Backfill existing rows that would have the column as NULL
7
+
3. Make the column not nullable and add a new index
8
+
9
+
To install it:
10
+
```bash
11
+
$ bin/rails solid_queue:install:migrations
12
+
```
13
+
14
+
Or, if you're using a different database for Solid Queue:
From this version onwards, when a worker is killed and the supervisor can detect that, it'll fail in-progress jobs claimed by that worker. For this to work correctly, you need to run the above migration and ensure you restart any supervisors you'd have.
24
+
25
+
1
26
# Upgrading to version 0.5.x
2
27
This version includes a new migration to improve recurring tasks. To install it, just run:
0 commit comments