ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #pm2
Learn how to run multiple instances of a Node.js app with PM2 in cluster mode, verify the setup, and perform seamless reloads without dropping connections.
Learn how to use PM2 Cluster Mode to eliminate deployment downtime. This guide covers ecosystem configuration, rolling restarts, and the necessity of stateless architecture.
Stop dropping requests during deployments. Learn how to use PM2 cluster mode and rolling reloads to achieve zero-downtime updates for Node.js apps.
A hands‑on diagnostic guide to troubleshoot PM2 cluster mode misbehaviors like uneven load, memory restarts, and CPU imbalance. Follow step‑by‑step checks, fixes, and escalation paths to keep Node.js apps running smoothly.
PM2 cluster mode uses all your CPU cores and `pm2 reload` deploys without dropping requests — but only if your app honors the shutdown contract. Here's the config, the code, and how to verify it.
Stop letting your multi-core server go to waste. Learn how to use PM2 Cluster Mode to scale Node.js applications, achieve zero-downtime reloads, and handle the challenges of distributed state.
A concise architecture note for running a Node.js API with PM2 cluster mode: requirements, minimal config, trust boundaries, operational checks, and failure triggers.
PM2's zero-downtime reload mechanism sequentially restarts process instances in cluster mode to maintain application availability. While this ensures the service remains online, it creates a period where multiple versions of the application code coexist during the transition. When a deployment includes a destructive database schema change, the remaining acti
Goal Deploying a new application version that includes a database schema change requires that the rollback process also revert the migration. PM2’s pm2 deploy command can roll back application code, but it does not touch the database. Constraints and Uncertainty Rollback only reverts the last commit, leaving the database in the new state. A mismatch between
nodejs