Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stats timeout in 1 hour but actual processing has no timeout #385

Closed
betelgeuse opened this issue Sep 2, 2012 · 3 comments
Closed

stats timeout in 1 hour but actual processing has no timeout #385

betelgeuse opened this issue Sep 2, 2012 · 3 comments

Comments

@betelgeuse
Copy link
Contributor

betelgeuse@pena /mnt/checkouts/sidekiq $ git grep EXPIRY | cat 
lib/sidekiq/processor.rb:          conn.setex("worker:#{self}:started", EXPIRY, Time.now.to_s)
lib/sidekiq/processor.rb:          conn.setex("worker:#{self}", EXPIRY, Sidekiq.dump_json(hash))
lib/sidekiq/util.rb:    EXPIRY = 60 * 60

This means that long running jobs will not show up in stats after one hour. @mperham is still some kind of a leftover or what is the logic here?

@mperham
Copy link
Collaborator

mperham commented Sep 2, 2012

What is a better expiry time?

@betelgeuse
Copy link
Contributor Author

I would change it to have no expiry and use del when it's done processing. If the worker crashes there is already cleaning code based on pid. Sounds ok?

@mperham
Copy link
Collaborator

mperham commented Sep 2, 2012

I don't like putting data in redis with no expiry. A one week expiry is ok if it is removed when complete under normal circumstances.

@mperham mperham closed this as completed in ba2470e Sep 9, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants