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
Percy6mo ago
Project ID: 7073773c-bae3-4648-b179-72dda4777e8b
StonkStoic
StonkStoicOP6mo ago
7073773c-bae3-4648-b179-72dda4777e8b
Brody
Brody6mo 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
StonkStoicOP6mo ago
Okay but what’s the root cause,
Brody
Brody6mo 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
StonkStoicOP6mo ago
Got it
Brody
Brody6mo ago
does your service have a volume attached?
StonkStoic
StonkStoicOP6mo ago
Sorry didn’t get this question
StonkStoic
StonkStoicOP6mo ago
Nope This isn't there yet
Brody
Brody6mo ago
have you since switched to the v2 runtime?
StonkStoic
StonkStoicOP6mo ago
Not yet. Is it like safe? To shift production to v2?
Brody
Brody6mo ago
its beta but if it fixes your issue its safer than the legacy runtime
StonkStoic
StonkStoicOP6mo ago
Okay anything to read on what changed in v2?
StonkStoic
StonkStoicOP6mo 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
Brody6mo ago
the option would be under deploy or you can just search for runtime
StonkStoic
StonkStoicOP6mo ago
Changed now. Will report back if anything breaks/everything works 😄
Brody
Brody6mo ago
yes please do!
StonkStoic
StonkStoicOP6mo ago
It got stuck yesterday again
Brody
Brody6mo 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
Want results from more Discord servers?
Add your server