Error: Acquire Timeout Exceeded for queued queries.

[tediousjs]

Error: Acquire Timeout Exceeded for queued queries.

[ben-page]

Does that mean I should not run queries more than max connections in pool

In general, no. It does not mean that. But I would not allow slow queries to take all of the available connections. No other work can get done. This is the purpose of the timeout: to throw an error rather than just wait forever for a connection.

I'm not sure what you are trying to do. But you could create a dedicated connection pool for your slow queries and disable the acquire timeout. But be careful. If one of your queries creates a deadlock or has an infinite loop, you'll never know. The connection pool will just wait forever.

Also from this example, there shouldn't be any available connections for i=3,4,5. So those queries should have waited for connections to be released and available into the pool.

That's right. 0,1,2 get the connections immediately. When any of those 3 connections are released, it will be made available to 3,4,5.

[ben-page]

Looks like this is working as intended. The acquire timeout is how long acquire will wait for an available connection.

[ankurgupta4891]

Does that mean I should not run queries more than max connections in pool ? I think acquire time should start when there is a free connection available and a query request is trying to acquire a connection from the pool, but it seems if there are more queries than no of connections in pool, many queries (that couldn't get connections) will die because of acquire time out. What is ideal way to queue queries then?

[ankurgupta4891]

Also from this example, there shouldn't be any available connections for i=3,4,5. So those queries should have waited for connections to be released and available into the pool.

[ankurgupta4891]

I get your point and understood acquire time out definition totally wrong. Thank you so much for clarification.

[ben-page]

No problem.