Selwin Ong

Because RQ uses Redis to store worker and job states, it's expected that RQ jobs will go into an inconsistent state if Redis doesn't work properly. I don't think there's...

If the issue is about addressing the part when a job gets popped, it could get orphaned because it no longer belongs in any queue/registry (and not Redis errors causes...

Yes, you can create a specific queue, for example "high-perf" and sends jobs to that specific queue. You'd then obviously configure only your high performance boxes to accept jobs from...

@sjwhitmore thanks for the clarification. I'll reopen this issue. I don't have any short term solutions for this, but here are my thoughts on possible implementations: 1. How do we...

> Wondering whether there's a specific design/technical reason for not being able to configure the maintenance tasks interval and the cleaning lock TTL. @ronlut no specific reasons as to why...

Sorry for the late response, no definitely not the intended behavior ;)

`worker.work()` itself does not accept `pipeline` argument. You'll need to be more specific as to which Redis commands that RQ uses that's not supported by Redis cluster.

What kind of features specifically do you need in implementing custom registry classes?

Well, there have been requests about adding support for namespaces. I suppose this is something we can consider, so you can do something like: ```python queue = Queue(name='foo', namespace='bar', connection=Redis)...

I have actually not tested this myself. Are you implying that RQ's default worker would use the new version of the code whenever there's code changes, but not `SimpleWorker`?