Closed vhgn closed 9 months ago
Error: failed to connect to database. err: failed to execute SQL: SELECT 1;
Post "https://***db***-**username**.turso.io/v2/pipeline": context deadline exceeded
I get this output in CLI
This simple trick showed that I don't get a response back
console.log("Got request")
const { rows } = await db.execute(`
SELECT name
FROM genres
`);
console.log("Got rows", rows);
It never outputted "Git rows..."
@vhgn can you check it now?
It worked! Thanks for the quick response. Is there anything done wrong on my side? How can I help preventing this happening in the future?
no problem on your side, it was a network connectivity issue of our cloud provider, we have run an automation to fix all clusters that had this issue, but apparently the automation haven't catch all of them. Thanks for reporting
Does having a starter plan versus a scaler plan have an impact?
in a sense yes, because scaler plan clusters don't have scale to zero or group sleeping, and this particular issue wouldn't have happened if it wasn't for a problem when scaling from zero. But this is not the quality of service that we wish to serve to our free tier users anyway. So my apologies
Issue
Production database does not respond