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/running-queues.md
+4-2
Original file line number
Diff line number
Diff line change
@@ -65,11 +65,13 @@ This way, worker will consume jobs with the `low` priority and then with `high`.
65
65
66
66
### Running many instances of the same queue
67
67
68
-
As mentioned above, sometimes we may want to have multiple instances of the same command running at the same time. The queue is safe to use in that scenario with all databases if you keep the `skipLocked` to `true` in the config file. Only for SQLite3 driver this setting is not relevant.
68
+
As mentioned above, sometimes we may want to have multiple instances of the same command running at the same time. The queue is safe to use in that scenario with all databases as long as you keep the `skipLocked` to `true` in the config file. Only for SQLite3 driver, this setting is not relevant as it provides atomicity without the need for explicit concurrency control.
69
+
70
+
The PHPRedis and Predis drivers are also safe to use with multiple instances of the same command.
69
71
70
72
### Handling long-running process
71
73
72
-
If we decide to run the long process e.g. with the command:
74
+
If we decide to run the long process, e.g., with the command:
0 commit comments