When are connections to the cluster available during the moving of a branch?
For several minutes the branches are moving to a newly provisioned cluster. When are new connections to the branch made to the cluster?
30 Replies
hi, looking into it now
I see the branch move error out, I'm going to cancel it for now as it might be a transient issue
could it be a version mismatch?
i accidentally provisioned the cluster 1 minor version below what the shared cluster has
for now the error is a connectivity issue, like at networking level. I'm checking if it's maybe something transient or a mis-configuraion on our side
The goal is to scale more since we went live and ran into scalability issues due to max concurrent connections.
aha, let me then see if I can increase that temporarily for you on the shared cluster, while we figure this out
one sec
thank you!
the affected branch is called "main"
and dbname is partner-tool, right?
Yes, that's correct.
do you have a rough idea of how many connection you'd need? Also double checking: you are hitting an issue with the connections over the wire protocol, not the concurrency limit over the API, correct?
the problem is, with vercel we have no idea how many serverless functions are actually created.
yes, we are directly connecting over tcp.
ok, I've increased it to 50, let me know if that seems to help
from vercel it might be better to use our SQL over HTTP proxy for this reason
we have also reduced the pg pooling "max" setting from 5 to 3.
the problem is, we are frequently using transactions where we run code in between (drizzle-orm)
I see, gotcha
this is something we cannot currently do over http afaik
yes, that's correct
ok, then let's see if 50 helps, in the meantime we'll see what went wrong with the branch move
let me know what you see on your side