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

Option to Disable "lockfile" check #99

Open
nebojsac opened this issue Feb 23, 2018 · 3 comments
Open

Option to Disable "lockfile" check #99

nebojsac opened this issue Feb 23, 2018 · 3 comments

Comments

@nebojsac
Copy link

Hi there,

I've started using it, and we have a lot of crontabs that we're gradually migrating over to Jobby (great tool btw).

One situation we just ran into was that some jobs are allowed to overlap, or to run as duplicates. This is because we have processes that get killed after running for 1h, but they get a SIGTERM signal and only terminate once they finish what they're doing. This prevents the next instance from starting up.

If there isn't an option to disable the lockfile check in the configuration for certain tasks, I'd gladly look at creating a PR - just let me know if you think this makes sense to add.

@BillBuilt
Copy link

This is exactly why I came here today - we need jobs to overlap too. Any way to achieve this?

@nebojsac
Copy link
Author

It would have to be changed in the core, I believe. Needs to have an option to not check for a lock file.

The way I'm solving this for now is to have alternating tasks with different names, even if it's essentially the same script.

Alternatively, I set the script to run for 59 minutes, instead of a full 1h, but this doesn't always help.

@wujekbogdan
Copy link

@nebojsac
There's a workaround. You can use the environment setting and give it a random value.
#86 (comment)

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

3 participants