dlr-eoc / prosEO

prosEO – A Processing System for Earth Observation Data
GNU General Public License v3.0
14 stars 1 forks source link

Planner does not receive job log from Kubernetes (high load?) #79

Closed tangobravo62 closed 8 months ago

tangobravo62 commented 4 years ago

During the S2 test campaign the Production Planner did not receive logs from Kubernetes for successful jobs:

prosEO (S2)> job step show -v 247
---
id: 248
version: 4
name: "proseojob248"
jobId: 247
jobStepState: "COMPLETED"
outputParameters: []
processingMode: "generate_datastrip"
inputProductClasses:
- "L1C_DS"
outputProductClass: "L2A_DS"
processingStartTime: "2020-06-23T16:33:15"
processingCompletionTime: "2020-06-23T16:33:34"
stdoutLogLevel: "INFO"
stderrLogLevel: "INFO"
processingStdOut: null
processingStdErr: null

To be checked whether this could have been due to high load conditions? (Many orders were generated in a short sequence.)

tangobravo62 commented 3 years ago

A similar issue was observed for Sentinel-5P where long-running job steps did not receive the job step log until after completion. An example is shown in the attached screenshot.

Bildschirmfoto 2021-05-25 um 16 41 15
katharinabassler commented 1 year ago

Issue has been resolved for GUI, but potentially not for CLI.

tangobravo62 commented 8 months ago

Not relevant for CLI. Issue closed.