Resque workers die with Redis reconnect errors after kill -HUP
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 456
- Forks
- 149
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 3
Description
After I issue kill -HUP to the master process, I get an endless loop of workers that fail to start with the following error:
Failed to start worker : #Redis::InheritedError: Tried to use a connection from a child process without reconnecting. You need to reconnect to Redis after forking.
I'm trying to dig deeper and find out what's going on, but not getting too far. The initial batch of workers start up and process jobs just fine, but after a HUP nothing can start.
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
Start by reproducing the HUP restart from the master process and trace the worker startup path around the reported Redis::InheritedError. Compare the initial worker launch with the post-HUP launch; done means workers restart successfully after HUP and can process jobs without Redis reconnect errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, ruby
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100