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
Currently when I deploy sidekiq is set to 'quiet' but force stopped shortly after. This means that some of my longer running jobs are killed and restarted (in some cases sending 2 notifications to users).
Is there a way to get the deployment to wait for the busy queue to be empty after quiet command has been sent and the rest of the deployment proceeding?
The text was updated successfully, but these errors were encountered:
Currently when I deploy sidekiq is set to 'quiet' but force stopped shortly after. This means that some of my longer running jobs are killed and restarted (in some cases sending 2 notifications to users).
Is there a way to get the deployment to wait for the busy queue to be empty after quiet command has been sent and the rest of the deployment proceeding?
The text was updated successfully, but these errors were encountered: