[DOCS-11282] Add sharding metadata refresh metrics section to serverStatus (SERVER-28670) Created: 05/Feb/18 Updated: 29/Oct/23 Resolved: 06/Jun/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.2, 3.6.4, 3.4.15 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kay Kim (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | add | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
https://docs.mongodb.com/manual/reference/command/serverStatus/ |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 36 weeks ago | ||||||||
| Epic Link: | DOCS: 4.0 Server | ||||||||
| Story Points: | 0.4 | ||||||||
| Description |
Documentation Request Summary:This change introduce a new shardingStatistics server status section, with the following contents:
Scope of changes:Impact to other docs outside of this product:MVP:Resources:Scope of changes:Impact to other docs outside of this product:MVP:Resources:Engineering Ticket Description:Sharding metadata refreshes have occasionally been demonstrated to cause throughput stalls. Currently, there is no visibility into when these are happening other than looking at the server log and trying to match them with FTDC data. In order to improve diagnosability we should introduce metadata refresh metrics to serverStatus so they can also be recorded in FTDC. All the proposed metrics should be under a section called shardingStatistics and will behave like this:
|
| Comments |
| Comment by Githook User [ 06/Jun/18 ] |
|
Author: {'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 06/Jun/18 ] |
|
Author: {'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 06/Jun/18 ] |
|
Author: {'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}Message: |