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
I believe messenger:stop-workers should be waiting by default (or optin --wait) for workers actually to be stopped (while true check if redis flag is cleared)
Currently a pre-deploy container can be finished before workers are stopped, causing the deploy to trigger while a worker job is processing still.
It's not ideal :)
Example
No response
The text was updated successfully, but these errors were encountered:
note to self; sometimes we also want to stop workers but keep the process alive, e.g. when updating the queue server. The workers should be resumed manually after upgrading.
Description
I believe
messenger:stop-workers
should be waiting by default (or optin--wait
) for workers actually to be stopped (while true check if redis flag is cleared)Currently a pre-deploy container can be finished before workers are stopped, causing the deploy to trigger while a worker job is processing still.
It's not ideal :)
Example
No response
The text was updated successfully, but these errors were encountered: