[DOCS-16026] [Server] Investigate changes in SERVER-73610: Introduce connection-leasing from ConnectionPool and NetworkInterface Created: 10/Apr/23  Updated: 13/Nov/23  Resolved: 19/Jul/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, 6.0.6, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Corry Root
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-73610 Introduce connection-leasing from Con... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCS-16275 [SERVER] Backport DOCS-16026 to v6.0. Backport Sub-Task Closed Corry Root  
Participants:
Days since reply: 29 weeks, 1 day ago
Story Points: 2

 Description   
Original Downstream Change Summary

We added some new information to the output of the connPoolStats command to track the "leased connection" concept introduced by this ticket.
"Leased connections" are those that have been loaned-out by some particular pool to some server-subsystem. These connections are not available to the pool, because they are on-loan, but may not be actively in-use running operations. They are expected to be returned to the pool at some point. The particular changes are:

  • A new top-level "totalLeased" field that is an integer counter of the total amount of connections currently on-lease
  • For each entry in the "pools" sub-document, a field "poolLeased" that is an integer counter of the amount of connections currently on-lease from that pool
  • For each entry in the "hosts" sub-document, a field "leased" that is an integer counter of the amount of connections to that host currently on-lease.

    Description of Linked Ticket

    Modify the ConnectionPool to allow connections to be "leased" from it. "Leasing" a connection from the pool should be just like the ordinary checking-out of a connection from the pool, but the connection pool's metrics and tracking should not assume that these connections are in active use for the duration of their lease, and should be exempted from related metrics.

Then, extend the NetworkInterface API to allow users to lease a connection from it's underlying pool. 



 Comments   
Comment by Corry Root [ 18/Jul/23 ]

george.wangensteen@mongodb.com

I added the new connPoolStats metrics to the following page:

connPoolStats

BUILD

Comment by Corry Root [ 14/Jul/23 ]

https://www.mongodb.com/docs/v6.0/reference/command/connPoolStats/

Comment by Sarah Olson [ 12/Apr/23 ]

No worries and thanks for confirming george.wangensteen@mongodb.com. This makes sense and we'll add it to our documentation requirements for 7.0. 

Comment by George Wangensteen [ 12/Apr/23 ]

Hi sarah.olson@mongodb.com  - sorry about that. This ticket was not generated an error. During implementation, we realized that we make a small change the metrics output for this one command (connPoolStats) to make the implementation we chose consistent with the remainder of the command output. 

I hope this isn't too much of a problem and I'm sorry I didn't see this coming at the time of our discussion on the PM ticket. We don't anticipate any other documentation impact for the project. Thanks for your help. 

Comment by Sarah Olson [ 10/Apr/23 ]

This documents https://jira.mongodb.org/browse/SERVER-73610, which is part of PM Epic https://jira.mongodb.org/browse/PM-3147

george.wangensteen@mongodb.com, in our discussion in the PM Epic comments, you confirmed that there was no documentation impact for this ticket. Was this documentation ticket generated in error, or did something change for the larger PM epic? Thanks very much for any input!

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