Closed
Bug 1306990
Opened 8 years ago
Closed 8 years ago
Generic Worker should terminate its host instance if it has been idle for a configurable period of time
Categories
(Taskcluster :: Workers, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: grenade, Assigned: pmoore)
Details
many gecko-t-win* instances are staying alive long after they have stopped taking on tasks thus wasting ec2 resources. g-w should halt its host instance after a configurable period of time and after a sane default (15 minutes?) if no configuration setting exists.
Assignee | ||
Comment 1•8 years ago
|
||
This must be a bug - it should already be doing this. I'll hop on a worker and see if I can figure out why it isn't doing that.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → pmoore
Assignee | ||
Comment 2•8 years ago
|
||
Rob, Have you seen any more occurrences of this? I believe this is fixed with the new refactoring of the generic worker. Pete
Flags: needinfo?(rthijssen)
Reporter | ||
Comment 3•8 years ago
|
||
yes, recent g-w releases do terminate correctly on idle
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(rthijssen)
Resolution: --- → FIXED
Updated•5 years ago
|
Component: Generic-Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•