Suggestion: allow signaling to remote workers
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 9.5k
- Forks
- 1.7k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 25
Description
Changing the queue_empty hook to execute each time state_change is called, or allowing the heartbeat thread to pickup instructions targeted at a particular worker, passed through Redis would allow for shutdown of remote workers, which would be ideal for developers running workers in remote docker containers.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing the queue_empty hook, state_change calls, and the heartbeat thread, then inspect how Redis could carry worker-specific instructions. Done should mean a developer can signal and shut down a worker running in a remote Docker container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, ruby
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100