[SERVER-71685] Remove ConnectionAcquisitionToWireLoggingRate parameter Created: 29/Nov/22 Updated: 29/Oct/23 Resolved: 06/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc4, 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Backport Requested: |
v6.2
|
||||||||||||||||||||||||
| Sprint: | Service Arch 2022-12-12 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||
| Description |
|
Currently, the ConnectionAcquisitionToWireLoggingRate parameter is set to 0.2 by default which is quite high since it means we are sampling 20% of egress connections to emit a metrics log message. This could end up being problematic for customers. |
| Comments |
| Comment by Githook User [ 09/Dec/22 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: (cherry picked from commit 8cefa36fddf8cad897d669a565038cd0ae0c83a2) |
| Comment by Githook User [ 06/Dec/22 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |
| Comment by Jason Chan [ 01/Dec/22 ] |
|
This patch will remove the connectionAcquisitionToWireLoggingRate server parameter. The new behavior is that the metric will only be be logged if the connectionAcquisitionToWire time is over the threshold of 1ms. |
| Comment by Githook User [ 01/Dec/22 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |