[GODRIVER-1926] GetFailed event does not always return correct reason Created: 19/Mar/21  Updated: 28/Oct/23  Resolved: 30/Mar/21

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

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


 Description   

If the connection pool is empty and the connect call on the newly created connection fails, we publish a GetFailed CMAP event. This event's Reason field should be set to ReasonConnectionErrored.

Incorrect event construction is at https://github.com/mongodb/mongo-go-driver/blob/a62c7d7c704d9269a5399f80e266fdefb4f5da39/x/mongo/driver/topology/pool.go#L443.



 Comments   
Comment by Githook User [ 30/Mar/21 ]

Author:

{'name': 'Divjot Arora', 'email': 'divjot.arora@10gen.com', 'username': 'divjotarora'}

Message: GODRIVER-1926 Fix Reason field in GetFailed CMAP events (#627)
Branch: release/1.5
https://github.com/mongodb/mongo-go-driver/commit/c317b0ca7c68c22bf1d62489497d480255d3133f

Comment by Githook User [ 30/Mar/21 ]

Author:

{'name': 'Divjot Arora', 'email': 'divjot.arora@10gen.com', 'username': 'divjotarora'}

Message: GODRIVER-1926 Fix Reason field in GetFailed CMAP events (#627)
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/aded83105269d3909cde56242ff1a61c440a4b05

Comment by Divjot Arora (Inactive) [ 30/Mar/21 ]

https://github.com/mongodb/mongo-go-driver/pull/627

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