[DRIVERS-2236] CMAP inconsistency when clearing load balanced pools Created: 12/Mar/22  Updated: 28/Oct/23  Resolved: 08/Apr/22

Status: Closed
Project: Drivers
Component/s: CMAP, Load Balancer
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Shane Harvey Assignee: Patrick Freed
Resolution: Fixed Votes: 0
Labels: size-small, spec-change
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by PYTHON-2933 Clarify clearing behavior for load ba... Backlog
Problem/Incident
is caused by DRIVERS-1942 Clarify clearing behavior for load ba... Implementing
Driver Changes: Not Needed

 Description   

DRIVERS-1942 added the following clarification to the CMAP spec section describing the "Clearing a Connection Pool" method:

This method MUST NOT be used in load balancer mode.

If the pool.clear() method is not used, then load balanced pools will never emit PoolClearedEvents. However, there is a load balancer spec test which asserts that a PoolClearedEvent is emitted after a connection handshake failure:
https://github.com/mongodb/specifications/blob/008d2f5/source/load-balancers/tests/sdam-error-handling.yml#L175-L205

What should a driver do when clearing a load balanced pool without a serviceId (eg when the initial hello command fails)? Is the load balancer test simply out of date?



 Comments   
Comment by Githook User [ 04/Apr/22 ]

Author:

{'name': 'Patrick Freed', 'email': 'patrick.freed@mongodb.com', 'username': 'patrickfreed'}

Message: DRIVERS-2236 Clarify load-balanced pool clearing behavior (#1167)
Branch: master
https://github.com/mongodb/specifications/commit/98db467cb8f2f7bf50e79fc563e59701a8b3e3bf

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