Closed jdries closed 1 year ago
Should be possible to use K8S cron job, but need a solution to register usage in marketplace.
As discussed:
Added a job-tracker CronJob to the spark-jobs namespace in Kubernetes. The JobTracker thread that ran in the Flask process has been disabled.
A workaround for the OpenEO web app relying on the JobTracker having downloaded the job results to disk is in place until #232 is implemented; this assumption no longer holds because they run in different containers now.
As discussed: usage reporting, relying on an ETL API, will be tackled in #272.
Job tracker is a micro service for batch job management. On K8S, job tracker tasks are still part of the main web service. We need to see how this can be deployed separately, and if that requires a nifi instance.