This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 222
Connection pool - Blocking operations #91
Comments
fwbrasil
changed the title
Connection pools - Blocking operations
Connection pool - Blocking operations
May 10, 2014
Okay, gonna get some work done on it this week and remove these blocking ops. |
any updates on these? |
@fernandezpablo85 any contributions are welcome :) But I do plan to check the possibilities here. |
@mauricio I was wondering, do you have plans to work on this in the short tem? It's a major issue for high-load systems, so I've been avoiding suggesting |
We have fixed this issue in jasync fork of the lib. see this issue: jasync-sql/jasync-sql#41 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The connection pool performs block operations to acquire and test connections using the connection factory [1] [2] [3] [4]. This characteristic makes the pool really sensible to database issues, like high latency or connection errors.
The workaround for me was:
I think that an ideal solution should be avoid having blocking operations inside connection pools.
[1]
postgresql-async/mysql-async/src/main/scala/com/github/mauricio/async/db/mysql/pool/MySQLConnectionFactory.scala
Line 53 in 2ab790d
[2]
postgresql-async/mysql-async/src/main/scala/com/github/mauricio/async/db/mysql/pool/MySQLConnectionFactory.scala
Line 124 in 2ab790d
[3]
postgresql-async/postgresql-async/src/main/scala/com/github/mauricio/async/db/postgresql/pool/PostgreSQLConnectionFactory.scala
Line 53 in 2ab790d
[4]
postgresql-async/postgresql-async/src/main/scala/com/github/mauricio/async/db/postgresql/pool/PostgreSQLConnectionFactory.scala
Line 90 in 2ab790d
The text was updated successfully, but these errors were encountered: