[SERVER-64968] Add a global counter to measure how many ingress connections the server has rejected for workload management Created: 25/Mar/22  Updated: 29/Oct/23  Resolved: 05/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: George Wangensteen Assignee: Reo Kimura (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by COMPASS-5999 Investigate changes in SERVER-64968: ... Closed
is depended on by TOOLS-3171 Investigate changes in SERVER-64968: ... Closed
Documented
is documented by DOCS-15526 Investigate changes in SERVER-64968: ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2022-07-11, Service Arch 2022-07-25, Service Arch 2022-08-08, Service Arch 2022-08-22
Participants:

 Description   

As we improve our workload management, particularly around connection management, the server will sometimes reject incoming connections if it doesn't have the capacity to handle them.  Let's add a counter to measure how many connections we've rejected for this reason. (Note this will let us see a time-series view of how many connections we reject for this reason over time in FTDC). Right now, it should be incremented when we reject connections due to reaching the maxConnecting limit, but there may be other places we'd like to increment it later. 


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