Project

Profile

Help

Issue #757

closed

How to stop workers on remote machine

Added by jluza about 9 years ago. Updated about 5 years ago.

Status:
CLOSED - WORKSFORME
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.5
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

If I stop workers on remote machine, reserved resources for these workers stay locked. I just been told, there's no way how to stop only specified workers in pulp. This could be quite issue because if some workers crash (from various reasons including hardware incident), resource stay locked even after restarting them.
I don't know of any ways how to remove reserved resource other from go directly into mongo and remove lock manually. This is quite impractical and also hard to do because we don't have (and won't have) direct access to mongo database.

Please consider this issue as also RFE of:
- way how to stop workers
- safety worker stop should be something like this: remove worker from db.workers - so it can't accept any tasks, [wait for running task], remove reserved
resources for this worker, kill worker

- way how to unlock reserved resources
- worker could have also list of reserved resources in memory. After restarting, worker would check in db if there's some reserved resources and then removed them. I don't think it's possible resume task after worker restart, so reserved resources wouldn't have to be reserved anymore.
- resource manager could also remove reserved resources in process of removing inactive workers.

Also available in: Atom PDF