R
Railway•6mo ago
t0dd

App working fine, but randomly becomes unresponsive for up to 1 minute.

We have a Node.js app deployed which works fine, memory & CPU usage is stable, but we have monitoring setup and we can see that a few times a day it fails to respond. This happens for up to one minute. What can cause this? This only started happening a week or two ago.
10 Replies
Percy
Percy•6mo ago
Project ID: N/A
t0dd
t0dd•6mo ago
We had some similar issues on Render, but after moving the codebase to Railway the issue was fixed for atleast a few weeks. Project ID: ec601a07-d4ed-4e1e-8ab2-5653a269d0f9
Adam
Adam•6mo ago
Are you logging? You should add some very extensive logging and monitor This sounds like a code issue given that this issue has persisted across platforms
t0dd
t0dd•6mo ago
Yeah we're doing pretty extensive logging Thing is this issue was resolved for around 2-3 weeks after we moved over to Railway And has only started to appear recently Code doesn't crash on, we see nothing else on Railway and no exceptions are logged
Adam
Adam•6mo ago
Do you log requests + time to complete?
t0dd
t0dd•6mo ago
12/04 is when we migrated from Render to Railway No issues for 2 weeks Then suddenly we get something similar as on Render just less frequent And we didn't really make any changes which could cause this
Adam
Adam•6mo ago
And memory/CPU metrics are stable + not maxed? This is very odd. Not sure what it could be. This help chat is for Railway help specifically and unfortunately this seems like a code issue, so there's not much I can help you out with here
t0dd
t0dd•6mo ago
Render told us it was a code issue as well 😃 Yep Saw unresponsiveness when CPU usage was like 20% We do have some spikes here and there but seems like not correlated to unresponsiveness If I look at commits from the 18th-21st, none changed anything except minor parts of certain routes.
Adam
Adam•6mo ago
It being a code issue doesn't necessarily mean that a breaking change was introduced in that time period, sounds like you've been having this problem for a while. There are many, many reasons why this could be happening and without full access to your stack, code, logs, etc I wouldn't be able to help. This is definitely a chronic issue with your code/stack. Given that it's very unlikely that it's an issue with Railway, there isn't much I can do to help you. You'll have to dig into your code and figure it out for yourself.
t0dd
t0dd•6mo ago
Thank you for your help.