Pain point · Reliability & bugs · Blocks work
Function executor loses sync with actual runtime containers
3 source threads · first seen 2022-03 · last seen 2023-10
Summary
The executor's table of active runtimes can fall out of sync with the real containers, so executions fail with a curl error and the inactive runtime deletion fails in the logs.
- Affects
- self-hosted function users
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“When you're testing a function, and you have to keep deploying it and running it, and constantly get the CURL error”
“It seems it's possible for the Appwrite Executor's table of active runtimes and the actual running runtime containers to go out of sync”
“An internal curl error has occurred within the executor! Error Msg: Could not resolve host”