Open-EO / Open-EO/openeo-python-client
Handle ConcurrentJobLimit errors more intelligently
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
geopyspark driver deployements typically have limit on max number of parallel jobs, and going over that limit might cause something like:
ERROR openeo.extra.job_management: 400 ConcurrentJobLimit: Job was not started because concurrent job limit (10) is reached.
the client could handle this more intelligently in some situations
e.g. back off a bit (instead of hard failing) when creating/starting new jobs in the job manager loop
Note however that ConcurrentJobLimit is not an official error code (yet) in openEO API, so pushing for that might be part of the work here.
related to
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 tracing the job manager loop responsible for creating or starting new jobs and reproduce the ConcurrentJobLimit response described here. Review openEO API errors.json and related issue 559 to determine how the error should be represented and handled. Done means the client backs off appropriately instead of hard-failing in the intended situations, with behavior aligned to the agreed API error semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100