[SERVER-81073] Add and log connection ID in connection pool Created: 14/Sep/23  Updated: 05/Dec/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Varun Ravichandran Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-77995 Log connection ID for pooled LDAP con... Blocked
Assigned Teams:
Service Arch
Sprint: Service Arch Prioritized List
Participants:

 Description   

The `ConnectionPool` interface has a notion of a `PoolId`, which is used to maintain separate pools for each `HostAndPort`. However, it does not seem to have a similar concept to distinguish between individual connections in each pool. As a result, many of the connection pool's logs (e.g., this one) address specific lifetime changes for individual connections (spawn, refresh, destruct) without providing a way to identify which connection this is happening to.

Incorporating a connection ID for each connection within a `SpecificPool` would help trace through individual connection lifetimes through logs so that it's easier to correlate operation success/failure with the connection that they used.


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