Closed
Bug 1399123
Opened 8 years ago
Closed 8 years ago
Enable/Disable workers
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hassan, Assigned: hassan)
References
Details
One of the actions we want to perform on a worker is disabling/enabling it. Disabling workers allows the machine to remain alive but not accept jobs so that a user could perform diagnostics/debugging on the machine. Enabling workers on the other hand will resume accepting jobs. Presently, when claimWork is called, a worker is updated with new tasks.
Refer to RFC#90[1] for the discussion.
[1] https://github.com/taskcluster/taskcluster-rfcs/issues/90
|
Assignee | |
Updated•8 years ago
|
Assignee: nobody → helfi92
|
|
Assignee | |
Updated•8 years ago
|
Status: NEW → ASSIGNED
|
||
Comment 1•8 years ago
|
||
Commits pushed to master at https://github.com/taskcluster/taskcluster-queue
https://github.com/taskcluster/taskcluster-queue/commit/38a6606dc8d11690ae3b692f5dd01b840324492d
Bug 1399123 - Enable/Disable workers
https://github.com/taskcluster/taskcluster-queue/commit/98e9b145a9077849ccbef648a431da9108c1e568
Merge pull request #198 from helfi92/disable-enable-workers
Bug 1399123 - Enable/Disable workers
|
|
Assignee | |
Updated•8 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
|
||
Updated•6 years ago
|
Component: Queue → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•