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
After upgrading Puma to version 5.0 in pull request #5178, which requires systemd (or a similar system), we've noticed that, on our staging server, stopping (or restarting) the Puma service with Systemd takes exactly 60 seconds (it used to take exactly 90 before we started using a Puma socket in pull request #5372).
This means requests to a Consul application might timeout while restarting Puma after deploying new code.
We haven't found the cause yet. We've tried using Type=notify in the systemd service, or upgrading to Puma 6, getting the same results.
The text was updated successfully, but these errors were encountered:
User Story
After upgrading Puma to version 5.0 in pull request #5178, which requires systemd (or a similar system), we've noticed that, on our staging server, stopping (or restarting) the Puma service with Systemd takes exactly 60 seconds (it used to take exactly 90 before we started using a Puma socket in pull request #5372).
This means requests to a Consul application might timeout while restarting Puma after deploying new code.
We haven't found the cause yet. We've tried using
Type=notify
in the systemd service, or upgrading to Puma 6, getting the same results.The text was updated successfully, but these errors were encountered: