Closed AFoletti closed 5 months ago
I just restarted that failed job and it finished in 28 minutes. Close to the time it took on INT
Such errors are often an unpredictable effect of the overall load on both the GitLab runners and Stardog itself.
Closing due to inactvity
Describe the bug We configured the cube "bfe_ogd100_kennzahlensharedmobility" on INT and managed to publish it with a CSV containing arounf 500k lines (some 30Mb of data). Step 2 (transformation) took about 30 minutes.
This morning I exported the cube from INT, imported it into PROD and uploaded the very same data. I started the transformation but I get a timeout after 2h30 minutes or work.
Now: why does this cube/data combination work on INT and not on PROD? Additionally: would it be possible to have a hint in the GUI that the process actually stopped because of a timeout (in the GUI was still "running" and I only got lucky to have someone show me the logs, otherwise I would have waited for another 4 hours...)
Thanks!
Affected functionalities (all that apply)
Relevant links
To Reproduce Steps to reproduce the behavior:
Expected behavior
Screenshots
Desktop (please complete the following information):
Additional context CC version 1.13.5 (16d1fae) on both INT and PROD
@PDumasBAR @aressera