App goes down even though the CPU and memory usage, is within limits.

Our app freezes again and again, with 3 workers and 3 replicas in each of our machines.
21 Replies
Percy
Percy4w ago
Project ID: 7073773c-bae3-4648-b179-72dda4777e8b
StonkStoic
StonkStoic4w ago
7073773c-bae3-4648-b179-72dda4777e8b
Brody
Brody4w ago
I have seen another user report this too, so far, switching to the v2 runtime in the service settings seems to have resolved it, please give that a try and report back!
StonkStoic
StonkStoic4w ago
Okay but what’s the root cause,
Brody
Brody4w ago
I unfortunately wouldn't have an answer, nor would I have a way to find out why, but it was not a promise, only a way to differentiate between a code issue and a platform issue
StonkStoic
StonkStoic4w ago
Got it
Brody
Brody4w ago
does your service have a volume attached?
StonkStoic
StonkStoic4w ago
Sorry didn’t get this question
StonkStoic
StonkStoic4w ago
Nope This isn't there yet
Brody
Brody4w ago
have you since switched to the v2 runtime?
StonkStoic
StonkStoic4w ago
Not yet. Is it like safe? To shift production to v2?
Brody
Brody4w ago
its beta but if it fixes your issue its safer than the legacy runtime
StonkStoic
StonkStoic4w ago
Okay anything to read on what changed in v2?
StonkStoic
StonkStoic4w ago
Thanks Let me have a look I guess we are already on it as I see no option in my currently deployed project under networking
Brody
Brody4w ago
the option would be under deploy or you can just search for runtime
StonkStoic
StonkStoic4w ago
Changed now. Will report back if anything breaks/everything works 😄
Brody
Brody4w ago
yes please do!
StonkStoic
StonkStoic3w ago
It got stuck yesterday again
Brody
Brody3w ago
then unfortunately that would mean there is an issue with your code, I would recommend adding extremely verbose debug logging so that you can narrow down the cause