-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database configuration and max connections #17
Comments
A starting point is the Check what value is currently set in there. |
Not sure how the JupyterHub on k8s affects things here. Note that each node has a unique internal IP ( |
I think what @jomey has pointed out here is what is going one. Something I didn't think of. |
Well I checked what the user had for max connections it was unlimited. As in the name of this issue @scottyhq made, the postgres config has a max_connection of.... 100 people. I just changed it to 500 |
I think the connections != people. It's a notebook that establishes a connection, so if you have 70 working on 4 parallel notebooks, then you will have 280 connections unless they shut down and restart their kernel |
I am not certain on this one and I doubt it exists, but maybe there is a 'idle_timeout' at which point SQLAlchemy shuts down the connection and re-connects if it is used again |
Yep per our convo, I just set the |
I am closing this issue in favor of continuing with the logged SnowExSql issue |
It seems like we can currently only have a limited number of simultaneous connections (not sure exactly how many or where this configuration lives). cc @micahjohnson150 @jomey @lsetiawan if you want to dig in.
the EC2 config is here https://github.com/snowex-hackweek/jupyterhub/blob/main/terraform/eks/ec2_postgres.tf and the actual database setup is probably documented over in https://snowexsql.readthedocs.io/en/latest/
Full Traceback
The text was updated successfully, but these errors were encountered: