[DOCS-1210] Better differentiation between ServerStatus outputs for sharded vs. nonsharded systems Created: 07/Mar/13 Updated: 30/Oct/23 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Osmar Olivo | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Description |
|
Differences in server status output meaning from replica sets to sharded clusters should be explicitly defined. For example, number of connections along with number of ops is specific to the mongos you run it on and not cluster-wide. As a result the implicit behavior and definitions are different when running on a replica set vs. a sharded cluster. New metrics being added to serverstatus() for 2.4 should also be doced, |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed by Emily Hall for Housekeeping on 7/27/16. Thank you! |