Rank 1: Thread
It just keeps running, and there's no way to manually stop it.
Votes
0
Replies
7
Participants
4
Messages
8
Rank 1: Thread
It just keeps running, and there's no way to manually stop it.
cc @Meldiron
Thanks for bringing this up 🙌 cc @Hemachandar
We will be trying to reproduce this next. @lucas can you confirm with me if those executions did what they were supposed to? Also, is it still processing now? I am trying to differenciate between three possible problems:
A) Execution never acutally started
B) Execution is not respecting timeout
C) Execution crashed, preventing from marking proper status (failed/succeeded)
We haven't been able to repro this issue - function gets timed out within the appropriate set limit.. nor we could set an invalid timeout value like 0 or null.
I suspect it has to do with worker crashing/restarting when the job is in progress which makes the process dangling.
@user could you investigate further on worker crash/restart if any? cc @Meldiron
Rank 1: Thread
Well its hard to tell because it happened in the middle of many other executions doing same job, so I'm not sure if they actually did their job. I can even see the logs because they are shown as Processing.
Its also hard to tell if they are still running, because execution is supposed to end after 50 loops in the code. But my GB-Hour usage isn't that high compared to execution time (still running).
Rank 1: Thread
Rank 1: Thread
I updated code to log somewhere else, so if same issue happens, i might be able to tell.
Rank 1: Thread
Same thing happened, and everything was fine. It executed without any errors