What’s interesting is that this question was asked before. And the Render.com staff instructed the user to take the conversation private and then locked the thread after 30 days.
I want to urge the Render.com staff to change their policy on the 30-day forum comment lockout. The status quo has the potential to generate a lot of long term negative value by producing a series of user problems into the forum that ultimately go unanswered. I wanted to come in and answer the question in this thread above… But the thread is locked!
It turns out that sqlalchemy’s default connection pooling is the nail gun of developer foot guns. It’s also infrequent and never triggers after a fresh app re-deploy, since non of the connections in the pool have had a chance to expire. I’m also guessing that this pattern is EXTREMELY common in python apps using a database. Really, the sqlalchmey devs should have chosen to use a NullPool by default since a connection pool is really a later stage optimization setting, but it is what it is.
I’m sure bugs of this scale exists in other tech stacks. And because of things like docker, Render.com can’t force a fix on it’s developers. So right now, the forum either here on Render.com’s or stack overflow (or similar) is where developers using Render.com will go. So please, until a question is answered, don’t close it off! 30 days is certainly too little of time.
Thanks for everything you guys do. Render.com is truly awesome!!