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
Hi,
When running an instance with the command node ace queue:listen, I noticed that upon sending a shutdown signal (SIGTERM), the instance continues to process new jobs that are added to the queue, even after receiving the signal.
Can someone explain to me how the shutdown process works with node ace queue:listen? Is there a graceful shutdown implemented to ensure that new jobs are not processed after the shutdown signal is received?
The text was updated successfully, but these errors were encountered:
Hi,
When running an instance with the command
node ace queue:listen
, I noticed that upon sending a shutdown signal (SIGTERM), the instance continues to process new jobs that are added to the queue, even after receiving the signal.Can someone explain to me how the shutdown process works with
node ace queue:listen
? Is there a graceful shutdown implemented to ensure that new jobs are not processed after the shutdown signal is received?The text was updated successfully, but these errors were encountered: