[DOCS-13278] Investigate changes in SERVER-44296: Report sufficient significant figures of Flow Control locksPerOp in FTDC Created: 10/Dec/19 Updated: 13/Nov/23 Resolved: 18/Feb/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3, 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: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | docs-administration, docs-grab-bag | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 51 weeks, 1 day ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
DescriptionDownstream Change Summary The serverStats flowControl.locksPerOp field has been replaced by flowControl.locksPerKiloOp (to ensure sufficient significant figures are reported in FTDC). Description of Linked Ticket Numerical data in FTDC is stored as 64-bit integers. Flow Control locksPerOp is a floating point value, and is rounded down to 0 in FTDC when its value is < 1. Some ways to ensure this are:
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 18/Feb/20 ] |
|
Author: {'username': 'kay-kim', 'name': 'Kay Kim', 'email': 'kay.kim@10gen.com'}Message: |