Last Comment Bug 1306990 - Generic Worker should terminate its host instance if it has been idle for a configurable period of time
: Generic Worker should terminate its host instance if it has been idle for a c...
Status: RESOLVED FIXED
:
Product: Taskcluster
Classification: Other
Component: Generic-Worker (show other bugs)
: unspecified
: Unspecified Windows
-- normal
: ---
Assigned To: Pete Moore [:pmoore][:pete]
:
: Pete Moore [:pmoore][:pete]
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-10-02 09:46 PDT by Rob Thijssen (:grenade UTC+2)
Modified: 2016-10-26 04:03 PDT (History)
1 user (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description User image Rob Thijssen (:grenade UTC+2) 2016-10-02 09:46:41 PDT
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.
Comment 1 User image Pete Moore [:pmoore][:pete] 2016-10-02 09:58:20 PDT
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.
Comment 2 User image Pete Moore [:pmoore][:pete] 2016-10-26 02:34:24 PDT
Rob,

Have you seen any more occurrences of this? I believe this is fixed with the new refactoring of the generic worker.

Pete
Comment 3 User image Rob Thijssen (:grenade UTC+2) 2016-10-26 04:03:26 PDT
yes, recent g-w releases do terminate correctly on idle

Note You need to log in before you can comment on or make changes to this bug.