Open-EO / Open-EO/openeo-python-client
more flexible job manager end state
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
With the new internal queue; jobs are automatically retried incase more jobs are created that the amount of allowed parallel jobs.
Since the job manager runs until all jobs end in finalized, start failed or error, it does not support the internal queueing.
Ideally we would build in some flexibility that allows the user to submit and track more parallel jobs than those supported with their standard account.
Can we make the 'end condition' on start_failed more flexible while not risking an endless loop?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the job manager's end-condition and internal queue/retry handling; no file or test is named in the issue. Define the behavior for submitting and tracking work beyond the account's parallel-job limit, including a bounded condition that avoids endless retries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100