USR2 signal is happening but my resque job is going to dirty exit

[Moneshs]

We are the running the resque-pool process once the termination of the pod we are using the signal usr2 and worker processing jobs is in the processing state but when we check in the redis it has marked as the dirty exit and my jobs in the processing state.

[PatrickTulskie]

I've seen this happen before in some k8s setups where the job takes too long to wrap up and winds up getting killed. Might want to tweak your pod killing timeouts and ensure the correct signals are being sent for rescue-pool (which is a different repo).

[Moneshs]

@PatrickTulskie Job takes usually 4-5 mins but my prestop script doesn't kill untill the jobs is completed. The problem is job is in the processing state i can see it ps aux but even it in the processing state its in the dirty exit. Its happens only when the pods is in terminated