Obtaining a connection from pool does not honour timeouts #184

edevil opened this Issue Jan 18, 2013 · 1 comment


None yet
1 participant

edevil commented Jan 18, 2013

When you have multiple threads/greenlets trying to fetch a connection from the pool, only one of them will be waiting on the queue with the specified pool_timeout. All the other ones will be stuck on "self._pool_lock.acquire()" which does not have a timeout.

When there are a lot of concurrent threads/greenlets the time spent while waiting for the lock will grow unbounded and both the query timeout and the pool timeout will not be honoured.

edevil commented Feb 16, 2013


edevil closed this Feb 16, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment