[GODRIVER-1299] minPoolSize causes driver not to connect to mongo Created: 04/Sep/19  Updated: 06/Sep/19  Resolved: 05/Sep/19

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: 1.1.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Bradley Wilson-Hunt Assignee: Divjot Arora (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends

 Description   

With minPoolSize, the driver just seems to hang for ever not respecting the connect/ping timeout.

 

docker run -e MONGODB_URI="mongodb://xxxx:xxx@xxx:27017,xxxx:27017,xxxx:27017/matchmaking-service?ssl=true&authSource=admin&maxPoolSize=100&minPoolSize=10" -e MONGODB_DATABASE=matchmaking-service -e S2S_TOKEN=ciccio -e MONGODB_CONNECT_TIMEOUT=10s -p 8081:8081 --cpus="1" --memory=100m 90aa968740fe {"app":"matchmaking-api","env":"test","message":"ciccio","severity":"INFO","timestamp":{"seconds":1567604480,"nanos":724255411},"version":"SNAPSHOT"} 2019/09/04 13:41:20 attempting to connect to mongo

 

It just hangs forever..

 

Without Pool Size:

docker run -e MONGODB_URI="mongodb://xxxx:xxx@xxx:27017,xxxx:27017,xxxx:27017/matchmaking-service?ssl=true&authSource=admin&maxPoolSize=100" -e MONGODB_DATABASE=matchmaking-service -e S2S_TOKEN=ciccio -e MONGODB_CONNECT_TIMEOUT=10s -p 8081:8081 --cpus="1" --memory=100m 90aa968740fe {"app":"matchmaking-api","env":"test","message":"ciccio","severity":"INFO","timestamp":{"seconds":1567604557,"nanos":285167813},"version":"SNAPSHOT"} 2019/09/04 13:42:37 attempting to connect to mongo 2019/09/04 13:42:37 successfully connected to mongo 2019/09/04 13:42:37 attempting ping {"app":"matchmaking-api","env":"test","message":"starting matchmaking-api-test at SNAPSHOT on 8081","severity":"INFO","timestamp":{"seconds":1567604557,"nanos":387613955},"version":"SNAPSHOT"}

 

Its worth pointing out that this issue can't be replicated on master.

 



 Comments   
Comment by Divjot Arora (Inactive) [ 06/Sep/19 ]

b.wilsonhunt@faceit.com 1.1.1 was released yesterday. The deadlock fix should now be available in the latest released version.

Comment by Esha Bhargava [ 05/Sep/19 ]

Same as GODRIVER-1234

Comment by Bradley Wilson-Hunt [ 04/Sep/19 ]

Is this going to be released in 1.1.1?  

 

Was there a planned date for that release?

 

 

Comment by Divjot Arora (Inactive) [ 04/Sep/19 ]

b.wilsonhunt@faceit.com The MinPoolSize option did cause a deadlock, which was recently fixed in GODRIVER-1234. This fix was backported to the release/1.1 branch in GODRIVER-1290.

Generated at Thu Feb 08 08:36:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.