Skip to content
This repository has been archived by the owner on Apr 1, 2023. It is now read-only.

Expiration does not seem to be working with status consistently #142

Open
ghost opened this issue Dec 19, 2018 · 1 comment
Open

Expiration does not seem to be working with status consistently #142

ghost opened this issue Dec 19, 2018 · 1 comment

Comments

@ghost
Copy link

ghost commented Dec 19, 2018

We are using 1.1.0 and we have long running jobs which are not getting their expiration set

After a first status:
>> redis.ttl "sidekiq:status:#{id}"
=> 1793

When finished
>> redis.ttl "sidekiq:status:#{id}"
=> 86368

I am not able to replicate consistently. But I have a test case that fails when running multiple times. Linking to this issue.

@MarceloCajueiro
Copy link

Same problem here. The job data is deleted before the right time here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant