Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix sigterm misbehavior #2629

Merged
merged 3 commits into from May 20, 2021
Merged

Conversation

ye-lin-aung
Copy link
Contributor

@ye-lin-aung ye-lin-aung commented May 12, 2021

Description

Closes 2222.
The current issue occurs if the server can't be started and raised exceptions before signal re-registration is done.I put the code to log the first line of back trace to gives consistent error log if there is some error in worker starts.

Your checklist for this pull request

  • I have reviewed the guidelines for contributing to this repository.
  • I have added (or updated) appropriate tests if this PR fixes a bug or adds a feature.
  • My pull request is 100 lines added/removed or less so that it can be easily reviewed.
  • If this PR doesn't need tests (docs change), I added [ci skip] to the title of the PR.
  • If this closes any issues, I have added "Closes #issue" to the PR description or my commit messages.
  • I have updated the documentation accordingly.
  • All new and existing tests passed, including Rubocop.

@ye-lin-aung
Copy link
Contributor Author

Starting from puma 5.x if worker crashes and exited, the cluster will try to restart the workers immediately without exponential time delay. I noticed puma will wait 1 sec in 4.x. Is it bug or expected behavior for 5.x?

@nateberkopec nateberkopec added bug waiting-for-review Waiting on review from anyone labels May 13, 2021
@nateberkopec nateberkopec merged commit 04e4b1a into puma:master May 20, 2021
@nateberkopec
Copy link
Member

No idea on the exponential time delay backoff... want to open a separate issue?

JuanitoFatas pushed a commit to JuanitoFatas/puma that referenced this pull request Sep 9, 2022
* Log error if worker can not be started

* Removed sleeping of worker

* Runned rubocop
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug waiting-for-review Waiting on review from anyone
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Raising from config.ru doesn't always behave the same
2 participants