Hey team. I was working in my app and did a routine refresh of some data in a table by running a truncate query and then following this I usually import new data from a CSV file back into that table through a separate query.
The truncate query got stuck and eventually timed out, now I'm unable to view the table contents inside the retool database GUI. If I click on the table the whole database page becomes unresponsive and refreshes take forever to get in and of course all my queries from the frontend are timing out because the data is inaccessible.
I see the below in the console:
Failed to load resource: the server responded with a status of 422 ()
Failed to load resource: the server responded with a status of 500 ()
Hey @wb123 - welcome to the community and thanks for reaching out.
This kind of unresponsiveness generally means that you've maxed out the number of connections to your DB, which does seem to be the case. I can restart the associated compute, but this might mean that your use case is starting to exceed RetoolDB's capabilities. It is intended to be convenient but not necessarily scalable.
Thanks Darren. Looks like it's all back. I appreciate the help and will look into moving the DB away from RetoolDB.
For future reference, do these services auto-restart after a period of time? Meaning if I were to encounter this again should I just give it some time to resolve?
Glad to hear it. Unfortunately, I think the DB will just hang in perpetuity when it maxes out like this, so your best bet is to reach out here, at least for the time being. This doesn't happen too often, but we've talked about giving org admins the ability to restart the compute via the Retool UI. It's just a simple API request so shouldn't be too difficult.
