ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how PM2's master process orchestrates graceful worker replacement, the role of SIGINT/SIGKILL, and why wait_ready matters for reliable deployments.
PM2 can reload Node.js workers without dropping requests, but only if the app is stateless and handles shutdown signals. Here is the practical checklist.
Learn how to launch a Node.js app with PM2’s cluster mode to utilize all CPU cores, gain automatic restarts, and improve fault tolerance.
PM2 cluster mode uses every CPU core and supports zero-downtime reloads, but only if your app is stateless and handles SIGINT. Here is how to configure it with an ecosystem file and verify it works.
PM2 Cluster Mode lets Node.js use all CPU cores by forking workers that share a port. This architecture note covers the minimal design, data boundaries, operational checks, failure modes, and when to move beyond it.
Learn how to configure PM2’s cluster mode so a Node.js service can be reloaded without dropping active requests, and understand the trade‑offs involved.
Cluster mode scales a stateless Node.js app across CPU cores with zero-downtime reloads; fork mode keeps in-process state safe. A decision table, ecosystem.config.js for both, and validation steps.
When one pm2 process is enough, what cluster mode demands from your app's state handling, and how to configure and verify zero-downtime reloads.
Learn how PM2’s cluster mode spreads Node.js workloads across CPU cores, verifies load‑balancing, and handles zero‑downtime reloads—plus the memory and state limits you must watch.
pm2
nodejs