A multi-cloud framework for big data analytics and embarrassingly parallel jobs, that provides an universal API for building parallel applications in the cloud ☁️🚀
Sometimes it happens that that some function call that i do fails unexpectedly, i.e I made some programming error which led to the lambda function not finishing.
I can kill the lithops process via ctrl + c, but does that kill the function (that might be on a infinite loop, for example)?
The problem is that after killing the lithops process and trying to reinvoke the job, it doesn't execute until i call it with a different runtime memory or the runtime in lambda is killed due a timeout error. My only guess is that lithops/aws is recognizing that the runtime is in a running state and the call doesn't execute.
Is it possible that lithops kills a function if the user has done ctrl + c to his local lithops process? Or that if a consecutive call is done over the same runtime, the runtime is "restarted"
Hello,
Sometimes it happens that that some function call that i do fails unexpectedly, i.e I made some programming error which led to the lambda function not finishing.
I can kill the lithops process via ctrl + c, but does that kill the function (that might be on a infinite loop, for example)?
The problem is that after killing the lithops process and trying to reinvoke the job, it doesn't execute until i call it with a different runtime memory or the runtime in lambda is killed due a timeout error. My only guess is that lithops/aws is recognizing that the runtime is in a running state and the call doesn't execute.
Is it possible that lithops kills a function if the user has done ctrl + c to his local lithops process? Or that if a consecutive call is done over the same runtime, the runtime is "restarted"