[DOCS-12795] Docs for SERVER-41460: dropConnections should shut down affected SpecificPools Created: 12/Jun/19  Updated: 13/Nov/23  Resolved: 10/Jul/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Steve Renaker (Inactive)
Resolution: Works as Designed Votes: 0
Labels: be
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-41460 dropConnections should shut down affe... Closed
Participants:
Days since reply: 4 years, 35 weeks, 1 day ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Description:

This change means that we could technically under represent active connections or dodge maxConns.

Engineering Ticket Description:

dropConnections() currently calls processFailure(). If it were to triggerShutdown() instead, then it would generate the same effect but officially indicate not to spawn new connections until someone requests one. It would also improve the reliability of drop_connections_replSet.js.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


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