Why is Puma starting in cluster mode... with --workers 1 ?
#1364
Comments
|
Yes. Single mode is In single mode, there is only one process. In cluster mode, you'll see a worker and master process. |
elenatanasoiu
added a commit
to elenatanasoiu/puma
that referenced
this issue
Jul 28, 2020
When starting to transition from Unicorn to Puma, I first tried out puma in development. I initially assumed from skimming the docs that the number of workers for single mode should be 1. This led to our developers not being able to kill their puma server properly in our dev environment via Ctrl+C since the master process would stick around and try to revive it. Upon reading the docs more carefully and checking out the issues, I found [I wasn't alone][issue-on-single-mode]. While it's obvious that 1 worker implies the existence of a master process, when you're just starting out it might take you a little while before you get your head around single mode versus cluster mode and having the configuration clearly stated helps with that imo. So to make it blatantly obvious how to run puma in single mode, I've added a line to the docs to explain it. [issue-on-single-mode]: puma#1364
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
puma --workers 1Expected behavior
[98939] Puma starting in single mode...Actual behavior
[98939] Puma starting in cluster mode...System configuration
Ruby version: 2.4.1p111
Is this intended behaviour?
Is there a difference between single mode and cluster moder with workers = 1?
The text was updated successfully, but these errors were encountered: