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

As a developer I want to provide the MultiBackendJobManager with a maximal run time for each job. #590

Closed
HansVRP opened this issue Jul 17, 2024 · 1 comment

Comments

@HansVRP
Copy link
Contributor

HansVRP commented Jul 17, 2024

Currently the MultiBackendJobManager, and batch jobs by extension to o not have a 'failsave' to avoid extremely expensive jobs.

What I propose is to measure the time how long a job is in running, and provide an input parameter to cancel the job in case it goes over the predicted runtime.

@soxofaan soxofaan transferred this issue from Open-EO/openeo-geopyspark-driver Jul 17, 2024
@soxofaan soxofaan linked a pull request Sep 3, 2024 that will close this issue
soxofaan added a commit that referenced this issue Sep 4, 2024
no support for `shift` on `time_machine` fixture below python 3.8

refs #590, #596, #578
soxofaan added a commit that referenced this issue Sep 5, 2024
Call public `run_jobs` instead of internal `_track_statuses`.
Use a fake backend that interacts with standard requests, instead of mocking internals.
Parameterize `cancel_after_seconds` instead of separate test functions

refs #590, #596
soxofaan added a commit that referenced this issue Sep 5, 2024
no support for `shift` on `time_machine` fixture below python 3.8

refs #590, #596, #578
@soxofaan
Copy link
Member

I think this ticket is done (with #596) and can be closed

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

Successfully merging a pull request may close this issue.

2 participants