Mike Perham

I don't document this because it starts to get into implementation detail. Anything I document becomes behavior I have to support and maintain backwards compatibility with. I always advise people...

Could you explain more? Long running jobs are pushed back to Redis by `Sidekiq::Manager`.

The jobs showing in Busy for hours later is because of the hard kill. Sidekiq's heartbeat is not fully transactional in order to minimize its runtime overhead, it uses `pipelined`...

...and that leakage is now fixed on main.

No idea. Never seen that error before.

Are you sure that's not a sidekiq-scheduler bug?

```diff - @count = Integer(env["SIDEKIQ_COUNT"] || Etc.nprocessors) + @count = Float(env["SIDEKIQ_COUNT"] || Etc.nprocessors).round ``` This will round to the nearest integer: 2.4 -> 2 and 2.5 -> 3. wdyt?

Sidekiq Enterprise 7.2.3 now available.

Is this Redis used for Sidekiq only? All transient Sidekiq data set a TTL (e.g. batch data, rate limiters, unique locks, process heartbeats). Global data structures (e.g. queues, retry, scheduled,...

Well, for instance the heartbeat is expired here: [> transaction.expire(work_key, 60)](https://github.com/sidekiq/sidekiq/blob/7b650ad0a21d801e61f125be632c41eff4a1f749/lib/sidekiq/launcher.rb#L175) Sidekiq Pro 4.x held dead batch data for 180 days, the same as the default dead timeout. This was...