ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Context PM2's graceful shutdown sends SIGINT to the master, waits kill_timeout (default 1600 ms), then issues SIGKILL. In cluster mode, workers only receive a graceful notice when the application explicitly handles the 'shutdown' IPC message during pm2 reload ; plain pm2 stop does not broadcast that message. Unresolved behavior The documentation does not spe
I am planning to migrate a small Node.js HTTP service from PM2 fork mode to cluster mode so deploys can use pm2 reload instead of stop/start, avoiding the brief listener gap a single forked process creates. The app will run as at least two cluster instances on Linux, with PM2 and Node versions pinned but not yet finalized. The plain HTTP path seems well unde
PM2 Cluster Mode utilizes the Node.js cluster module to distribute incoming connections across multiple worker processes. When the instances property is set to max in an ecosystem file, PM2 spawns a process for every logical CPU core detected on the host machine. While this maximizes CPU utilization, each worker operates as a separate process with its own me
When running Node.js applications in PM2 cluster mode, the master process coordinates worker instances and receives telemetry such as logs and custom metrics via an internal IPC channel. The goal is to understand whether the volume of IPC messages generated by high-frequency logging or metric emission introduces measurable event-loop lag in the individual wo
Problem In PM2 cluster mode, a worker that does not emit the ready signal during a pm2 reload causes the reload to hang or roll back. The reload process relies on listen_timeout to detect readiness and kill_timeout to terminate the old worker. However, the interaction between these timeouts and the worker’s shutdown hooks is not fully documented. Goal Unders
pm2
nodejs