Open carlosedp opened 4 years ago
Hi, did you try what I explained on slack yet? The timeout for deletions is around 3s but the watchdog stays holding for "write_timeout" seconds.
You need to deploy with a value lower than that. So try 1s.
Yes, when deploying with --env write_timeout=1s
the function gets removed correctly but by using the default (no write_timeout parameter) it fails.
Great. So it's a timing problem. We can't wait indefinitely to delete a container so it needs to have a limit, maybe a bigger limit than what's there now.
Trying to remove a function that is currently running (has a
RUNNING
task), fails.After trying to remove again, it succeeds.
Expected Behaviour
Function gets removed with first command.
Current Behaviour
Running function:
Deploy logs:
Trying to remove:
Logs:
Task gets stopped but container is not removed:
Running remove command again, removes:
Logs:
Possible Solution
Steps to Reproduce (for bugs)
1. 2. 3. 4.
Context
Your Environment
OS and architecture:
Versions: