[CDRIVER-2553] Verify that a network err during application operation doesn't initiate cooldown Created: 15/Mar/18 Updated: 27/Oct/23 Resolved: 22/Mar/18 |
|
| Status: | Closed |
| Project: | C Driver |
| Component/s: | libmongoc |
| Affects Version/s: | None |
| Fix Version/s: | 1.10.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
Related to recent PHP and Atlas issues. Ensure the C Driver matches the Server Discovery and Monitoring Spec: in single mode, if a network error disconnects the driver from a server while doing an application operation, the server's scanner node must not be put in "cooldown": the node is immediately eligible for checking during a scan, it is not banned for a 5-second cooldown. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 22/Mar/18 ] |
|
This is correct right now: in single mode, a network error when running a command calls mongoc_topology_scanner_node_disconnect, which does not set the scanner node's "last_failed" field, and therefore doesn't initiate cooldown. |