-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Issue 1: The View Jobs UI is limited to 200 jobs total, but MAAP is designed for users to run more than 200 jobs at once.
Issue 2: Given a 200 job window limitation, I would expect that the View Jobs UI would order the jobs in a consistent way (ideally prioritizing currently running and pending jobs?), so that when more than 200 jobs were recently issued (in state succeeded, running, accepted, failed, etc), refreshing the view would show the same set of running jobs at all times.
I ran 800 jobs yesterday. This morning, while maap.ListJobs() shows 5 jobs still running, the View Jobs UI shows a different number/subset of these running jobs when it is refreshed.
Issue 3: maap.ListJobs() also does not return a complete list of jobs. Though I ran 800 jobs within the last 48 hours, most finishing within the last 24 hours,
running = maap.listJobs(algo_id="job-gedi-tile-writer", version="amelia-deploy-w5eDQwev", status="Running").json()['jobs']
failed = maap.listJobs(algo_id="job-gedi-tile-writer", version="amelia-deploy-w5eDQwev", status="Failed").json()['jobs']
succeeded = maap.listJobs(algo_id="job-gedi-tile-writer", version="amelia-deploy-w5eDQwev", status="Succeeded").json()['jobs']yields
5 running jobs
10 failed jobs
10 succeeded jobs
This is very confusing as a user and also makes it difficult for me to write automation to poll and manage in-flight jobs.