Operational Defect Database
BugZero found this defect 33 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2643658
ftdc_connection_reuse.js considers dropped connections from other hosts
Last update date:
4/16/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
FTDC metrics per pool currently looks like this: "NetworkInterfaceTL-TaskExecutorPool-0" : { "poolInUse" : 3, "poolWasUsedOnce" : 0, "poolConnUsageTimeMillis" : 10, "ip-10-128-56-199.ec2.internal:20040" : { "inUse" : 0 }, "ip-10-128-56-199.ec2.internal:20041" : { "inUse" : 0 }, "ip-10-128-56-199.ec2.internal:20042" : { "inUse" : 0 }, "ip-10-128-56-199.ec2.internal:20043" : { "inUse" : 3 } } Each host currently has metrics for inUse, while each pool also has a poolInUse and a poolWasUsedOnce. We could add a wasUsedOnce metric to FTDC for each host, and this assert.soon could depend on the host's wasUsedOnce instead of a pool-wide poolWasUsedOnce. The easier fix here would be to just relax the assert.soon and add a comment considering it's possible that the connection servicing {find:"shards"} or other queries may add 1 or more to the poolWasUsedOnce connection count.
Top User Comments
JIRAUSER1260427 commented on Tue, 16 Apr 2024 14:04:04 +0000: CR: https://github.com/10gen/mongo/pull/21175
Steps to Reproduce
