lentaing@jimmy.harvard.edu wrote:

Hi,

We have deployed a local instance of Galaxy and have recently been experiencing several problems which we believe to be related to our server being overloaded with user requests. We get the following error message (from the log files):

raise exc.TimeoutError("QueuePool limit of size %d overflow %d reached, connection timed out, timeout %d" % (self.size(), self.overflow(), self._timeout)) TimeoutError: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 30

Could someone explain why we might get this error message and how we might configure our server settings to solve this problem?

Hi Len, You can increase the pool size with the following settings in the config file: database_engine_option_pool_size = database_engine_option_max_overflow = However, this may not really help. You will probably want to at a minimum enable external metadata: set_metadata_externally = True And consider running a multiprocess server.

Is universe_wsgi.ini.sample a configuration for production server instances? If not, could someone post some suggested settings for production servers (e.g. the settings that you use for the main galaxy instance http://main.g2.bx.psu.edu/)?

Full details on how to set up for a production server can be found in the wiki here: http://usegalaxy.org/production

Finally, is there a wiki page explaining the settings in universe_wsgi.ini?

No, but in a changeset a few months ago, I added commented descriptions to all options in the sample config file. If I missed anything or it's unclear, please don't hesitate to ask and we'll clarify. --nate

Thanks, Len

_______________________________________________ galaxy-user mailing list galaxy-user@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-user