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

Steps for debugging #38

Closed
fameoflight opened this issue Jul 13, 2018 · 4 comments
Closed

Steps for debugging #38

fameoflight opened this issue Jul 13, 2018 · 4 comments

Comments

@fameoflight
Copy link

I am using this in production. After few days it has stopped scheduling new jobs.

Any steps on debugging it?

@fameoflight
Copy link
Author

So what happened was the scheduler task failed because of bad config but it was never scheduled again until I scheduled it manually in rails console.

How can we prevent this from happening?

@hlascelles
Copy link
Owner

que-scheduler is a self scheduling job that operates in a postgres transaction, which includes parsing the config. If there was a config error then the job should have rolled back and tried again (indefinitely, if the config really was corrupt). The deletion / rescheduling of the job also happens in the same transaction.

It should not be possible for the job to ever "go away". Were any other operations being performed - could it have been cleared down if some other jobs were being deleted for some reason?

@hlascelles
Copy link
Owner

I've opened a PR change that will allow spec time configuration checks. Can you see if this will help with the issue you were seeing? #40

@hlascelles
Copy link
Owner

Version 3.2.2 released that covers invalid config checking.

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