Simon Taylor wrote: > Hi, > > What exactly are the two options database_engine_option_pool_size and > database_engine_option_max_overflow in universe_wsgi.ini?
Hi Simon, These are explained in the SQLAlchemy documentation: http://www.sqlalchemy.org/docs/05/reference/sqlalchemy/pooling.html > Occasionally I have a problem with galaxy timing out with an exception such > as: > TimeoutError: QueuePool limit of size 30 overflow 40 reached, connection > timed out, timeout 30 > > Checking the process list I don't see more than a couple of galaxy jobs > running so wouldn't expect 30+ connections to the db. > The timeout doesn't seem to resolve itself either and the only way to get the > site back is to kill and restart the process. Two things could help here: 1. Enable database_engine_option_strategy = threadlocal 2. Run additional Galaxy processes > Are there plans to handle the exception in any way and maybe reset the db > connection, or at least display a user friendly error message? It's probably possible to recover, although it's rarely a long term problem. Most people simply up the overflow or start an extra server and this fixes it. --nate > > Thanks, > Simon > | > | Systems utvikler > | Centre for Integrative Genetics (CIGENE) > | UNIVERSITETET FOR MILJØ- OG BIOVITENSKAP > > > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > > http://lists.bx.psu.edu/ > ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/