Kill sidekiq jobs by process id for busy jobs and by jid for other sets.

kill_sidekiq_job.rb

# FOR BUSY JOBS
# take the process_id from the /busy page in sidekiq and kill the longest running one.
workers = Sidekiq::Workers.new
long_process_id = 'integration.3:4:71111aaa111' # Eg: 'integration.3:4:71d1d7f4ef5a'
workers.each do |process_id, thread_id, work|
  process = Sidekiq::Process.new('identity' => process_id)
  process.stop! if process_id == long_process_id
end

# FOR SCHEDULED JOBS
# you need to know the jid to make this happen
jid = 'scheduled111aaa222' # Eg: 'e460064eda529b97e93314d4'
job = Sidekiq::ScheduledSet.new.find_job(jid)
job.delete # will just remove the job

# FOR RETRY JOBS
# you need to know the jid to make this happen
jid = 'retry111aaa222aaa' # Eg: 'e460064eda529b97e93314d4'
job = Sidekiq::RetrySet.new.find_job(jid)
job.delete # will just remove the job

you saved my life! I used the process.stop! to kill a stuck process

@patriciojofre haha 🤣 i get back to it each time i need to do this as well 👍

It works! 🥳

Thanks, gonna give this thing a shot. Appreciated!

Thanks

nice! helped me as well :)

It works, thanks!

I'm confused why you'd need to instantiate and loop through all of the workers (for the part specific to busy jobs). 😕

If you already know the process ID, why wouldn't you just do: Sidekiq::Process.new(identity: 'integration.3:4:71111aaa111').stop!?