Skip to content
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.

Connection pool - Blocking operations #91

Open
fwbrasil opened this issue May 10, 2014 · 6 comments
Open

Connection pool - Blocking operations #91

fwbrasil opened this issue May 10, 2014 · 6 comments

Comments

@fwbrasil
Copy link
Collaborator

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]


[2]
Await.result(item.sendQuery("SELECT 0"), configuration.testTimeout)

[3]
[4]

@fwbrasil fwbrasil changed the title Connection pools - Blocking operations Connection pool - Blocking operations May 10, 2014
@mauricio
Copy link
Owner

Okay, gonna get some work done on it this week and remove these blocking ops.

@fernandezpablo85
Copy link

any updates on these?

@mauricio
Copy link
Owner

@fernandezpablo85 any contributions are welcome :)

But I do plan to check the possibilities here.

@fwbrasil
Copy link
Collaborator Author

@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 quill-async to new users. I could give it a try if you don't have plans to work on it.

@kralikba
Copy link

kralikba commented Oct 6, 2016

@fwbrasil , @mauricio any updates on this?

@oshai
Copy link

oshai commented Nov 18, 2018

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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants