Pending batches expiring in 5 months, not 30 days about sidekiq HOT 6 CLOSED

Sidekiq Pro extends the batch's expiry to the dead job lifetime so the batch will not expire before any dead batch jobs have been garbage collected

Ahh, this makes sense! Maybe updating the Wiki will clear this up. 👍

from sidekiq.

My goal is to clear out these pending batches that we know will not succeed, so that we can get the admin UI back to being useful for looking at newer batches that may be stuck for different reasons.

If you have clear criteria for deleting batches, you can delete them from the Rails console:

Sidekiq::BatchSet.new.select {|b| b.description.match /^Full Title/ }.map(&:delete)
Sidekiq::BatchSet.new.select {|b| b.failures > 1 }.map(&:delete)
Sidekiq::BatchSet.new.detect {|b| b.bid == "S9yJ0GD2CW1TGw"}.delete

from sidekiq.

30 days is the default. The only way I know to change this value is to monkeypatch the Sidekiq::Batch::EXPIRY constant.

from sidekiq.

Batches with failures show in the UI that they expire in 5 months.

Created at for that batch 2024-05-02 18:19:08 138173/2097152 UTC.

from sidekiq.

Yup, thanks @raybaxter ours looks just like that as well.

from sidekiq.

This will happen if a batch job dies. Sidekiq Pro extends the batch's expiry to the dead job lifetime so the batch will not expire before any dead batch jobs have been garbage collected. See lib/sidekiq/batch/death.rb line 75.

from sidekiq.