|
26 | 26 | 'defaultRequeueTimeout' => 180, // 3 minutes |
27 | 27 | // Legacy: 'defaultworkertimeout' is deprecated but still supported |
28 | 28 |
|
| 29 | + // Threshold in seconds: a queue_processes row whose heartbeat (`modified` |
| 30 | + // timestamp) is older than this is treated as a dead worker by a |
| 31 | + // starting worker and cleaned up. Workers refresh their heartbeat every |
| 32 | + // loop, so a row not touched in this window almost certainly belongs to |
| 33 | + // a force-killed process. Intentionally much shorter than |
| 34 | + // defaultRequeueTimeout (which governs in-flight job requeueing). |
| 35 | + 'staleHeartbeatThreshold' => 90, // 90 seconds |
| 36 | + |
29 | 37 | // minimum time (in seconds) which a task remains in the database before being cleaned up. |
30 | 38 | 'cleanuptimeout' => 2592000, // 30 days |
31 | 39 |
|
|
63 | 71 | // set default datasource connection |
64 | 72 | 'connection' => null, |
65 | 73 |
|
| 74 | + // Multi-connection mode: whitelist of datasource connection names a |
| 75 | + // worker / job command may run against. Leave empty (or with fewer than |
| 76 | + // 2 entries) to stay in single-connection mode, where the singular |
| 77 | + // `connection` above (or 'default') is used. With 2+ entries, the first |
| 78 | + // is the default and any --connection passed to the run/job commands |
| 79 | + // must appear in this list or a RuntimeException is thrown. The admin |
| 80 | + // dashboard also exposes a connection switcher when this has 2+ entries. |
| 81 | + 'connections' => [ |
| 82 | + //'default', |
| 83 | + //'queue_secondary', |
| 84 | + ], |
| 85 | + |
66 | 86 | // enable Search. requires friendsofcake/search |
67 | 87 | 'isSearchEnabled' => true, |
68 | 88 |
|
|
0 commit comments