Rank 3: Container
Hi,
Sometimes functions are not being executed and being timed out. Can this happen because of less resources or something?
Votes
0
Replies
11
Participants
Unknown
Messages
12
Rank 3: Container
Hi,
Sometimes functions are not being executed and being timed out. Can this happen because of less resources or something?
Rank 3: Container
Function sometimes does not execute and gets timed out
Self-hosted?
Rank 3: Container
Yes
Rank 3: Container
Can this be due to high resource usage and resources not being available?
What are the logs of appwrite and openruntimes-executor
Yes
Rank 3: Container
Well there are many executions per minute and most of them go fine, only few go like this.
It could happened when too many function trying to execute at the same time occupying all workers.
Here you can see some possible explanation.
But it worth to track the errors in both containers I've listed above to eliminate all other causes.
Rank 3: Container
Thank you, there are not any error logs in openruntimes-executor except this.
Skipping runtimes stats loop due to error: Docker Error: EOF
and this one from appwrite, other are normal appwrite error, (user not logged in and etc..)
[2023-09-06 16:09:59 *83.74] WARNING swoole_signalfd_event_callback(): read from signalfd failed, Error: Resource temporarily unavailable[11]
So, yes this error is due to workers overload, you can see the details about it in the above issue
What are your server specs?