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.

Sign up for GitHub

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

Jump to bottom

Add jobflow name-based locking #30

Open
alexanderdean opened this issue May 29, 2017 · 2 comments
Open

Add jobflow name-based locking #30

alexanderdean opened this issue May 29, 2017 · 2 comments

Comments

@alexanderdean
Copy link
Member

This is a poor man's #17 - you use the EMR jobflow/cluster name to prevent multiple jobs from running at the same time. The jobflow will refuse to start if there is an existing running jobflow with the same name.
@alexanderdean alexanderdean added this to the Version 0.4.0 milestone May 29, 2017
@alexanderdean alexanderdean mentioned this issue May 29, 2017
Closed
@alexanderdean
Copy link
Member Author

This requirement was originally in the #20 ticket, but this morphed into file-based locking, so I've created this ticket for 0.4.0.

@BenFradet BenFradet self-assigned this Jan 17, 2018
@alexanderdean
Copy link
Member Author

Pushing back...

@alexanderdean alexanderdean removed this from the Version 0.4.0 milestone Jan 19, 2018
@BenFradet BenFradet added this to the Version 0.5.0 milestone Feb 13, 2018
@oguzhanunlu oguzhanunlu removed this from the Version 0.5.0 milestone Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alexanderdean @BenFradet @oguzhanunlu