Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sunset workers #55

Open
chrisnatali opened this issue Apr 15, 2016 · 2 comments
Open

Sunset workers #55

chrisnatali opened this issue Apr 15, 2016 · 2 comments

Comments

@chrisnatali
Copy link
Contributor

When a worker's models are out of date, it should be brought off-line in favor of new workers with up-to-date models.

Problems arise when jobs are running on workers scheduled to be sunsetted.

Does disabling access to Redis via removing ufw 'allow' rule prevent worker from taking new jobs off the queue? If so, this may be a way of taking out of date servers off line...to be 'reaped' later.

@chrisnatali
Copy link
Contributor Author

chrisnatali commented May 9, 2016

The following redis commands may help:
CLIENT LIST: List of connected clients
CLIENT KILL: Kill specified client

I noticed that upon terminating workers, there were still 'zombie' connections from workers that needed to be killed.

@chrisnatali
Copy link
Contributor Author

With the addition of the 'STOP_PROCESSING_QUEUE' command (part of the 0.5 release), this is partially addressed. By issuing 'STOP_PROCESSING_QUEUE' to a 'RUNNING' worker, it ensures that the worker will not pickup any new jobs while allowing it to complete the current job. Simplifying Sunsetting.

Leaving this open because this process still needs to be formalized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant