Selwin Ong

This is not a feature that's currently in RQ. Do you have any suggestions or ideas as to how we can implement this?

@aparcar the discussion in [this PR](https://github.com/rq/rq/pull/1412#issuecomment-786993853) also relies on resource sharing between workers so this is something we can work on long term.

Ok @aparcar . Let me know what you come up with.

> Rather than having individual queues it'd need a meta-state which contains a list of active jobs, or at least of active resources. In terms of active jobs, we can...

If you're running into load or IO issues, having more heartbeats is not the answer. Decreasing the worker TTL will actually cause more load because workers will try to dequeue...

So you have an external monitoring system that's monitoring RQ workers, got this. > Given that the heartbeat is hardcoded to occur 15 seconds before it's due, that doesn't provide...

Hey, rq-scheduler is no longer being developed.`rq-scheduler` was my first attempt in creating scheduling features in RQ, but sometime ago I build scheduling functionalities into [RQ here](https://github.com/rq/rq/blob/master/rq/scheduler.py#L30). The scheduler implementation...

I think there are two possibilities: 1. Custom callbacks for maintenance tasks 2. Enhance scheduled jobs so that support repeats with custom intervals. rq-scheduler already supports this but I wasn’t...

Not unless we patch `clean_registries()` to also check for worker PIDs to determine if a job is still being worked on. Would love to have a PR for this.

We should store in Redis as part of `Job`'s data. Should be something like `job.worker_pid`