Hey all,
Some of my jobs are in a queue for a few hour. Any update?
- j-e20e57fcfdb34947ad166725d76de1cc
- j-d6659193d588486ca27b3273b224a5b7
Hi Andrea,
I found your jobs. They triggered processing of CARD4L Sentinel-1 backscatter, which caused queueing initially, but that part is now done. I’m still figuring out why they do not go on with the next processing step.
You could try running the same job against our production endpoint (openeo.cloud), which should be up to date with some of the improvements we integrated for you.
best regards,
Jeroen
I found the root cause, and fixed it. Also triggered those two jobs again, they might still finish successfully.
Jobs submitted before the fix might be stuck in queued still, so let me know if you have any!
Hey Jeroen,
This job got queued again (ca.1h). Is there another problem?
- j-513ff586576b47fd92d1d8e5ac2e21ec
The job is indeed still waiting to start, cluster admins are checking if there’s a problem!
Super, let me know when it will be ready.
It actually started to run after 1.5h or so, but failed:
Invalid Extent: xmin must be less than xmax (xmin=-74.06828220890522, xmax=-179.99982833862782)\
The cluster admins looked deeper into it and applied another round of parameter tuning to try and fix the root cause. Fingers crossed that we get rid of this!
any update? 
Hi Andrea,
the situation seems to be better, but is not yet entirely fixed. We do have better monitoring in place so can notice faster when it’s occurring.
Did you still have noticeable issues or hanging jobs?