Unitech / Unitech/pm2

PM2 restart process irrespective of the set value of kill-timeout

Open
#5,130 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
43.3k
Forks
2.7k
PR merge metrics
No merged PRs in 30d

Description

What's going wrong?

It is a feature request, can we have some kind of pm2 reload or pm2 restart params (say --force) that can restart or reload the pm2 process irrespective of the kill-timeout value set for the process?

How could we reproduce this issue?

N/A

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the pm2 reload and restart command entry points, then inspect how the process kill-timeout is applied. Define the expected behavior of a --force parameter for restart or reload and verify that it can bypass the configured timeout without changing normal behavior; reproduction is not provided in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
backend, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.