init: respawn should try again after a while?
Bug #252997 reported by
Scott James Remnant (Canonical)
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Triaged
|
Wishlist
|
Unassigned | ||
upstart (Fedora) |
Won't Fix
|
Medium
|
Bug Description
Right now, "respawn limit" is a hard limit and will result in the job being stopped if execeeded.
Instead we should have something more of a rate limit, where we keep trying.
Related branches
Changed in upstart: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in upstart: | |
milestone: | none → 0.10 |
Changed in upstart (Fedora): | |
status: | Unknown → Confirmed |
Changed in upstart (Fedora): | |
importance: | Unknown → Medium |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
Personally, i think upstart should have both. In my environment, if an application/service is acting up (constantly restarting), at some point I'd like to give up on it.
Additionally, I'd like to add a "resting" time between start attempts. This is independent of the number of retries.
For instance:
Job 1 should retry every 10 seconds for 15 attempts, then give up.
and
Job 2 should retry every 30 seconds forever.
I believe that the current implementation is to count the number of respawn over an interval of time. If this is exceeded, the job is considered a run away and is stopped.