[SERVER-5787] Track opcounters (insert/delete/update) which results from sharding commands Created: 08/May/12  Updated: 09/Jul/16  Resolved: 02/May/14

Status: Closed
Project: Core Server
Component/s: Admin, Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kyle Banker Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: counters, sharding, stats
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-7382 Track counters for each command Closed
is related to SERVER-5828 Metric/Stats Tracking Closed
is related to SERVER-4868 Record more in config.changelog Closed
Participants:

 Description   

Currently we don't track these operations and it can lead to performance degradation without any indication in the counters.

It'd be really useful when troubleshooting to have a separate grouping of these opcounters for sharding operations.

It might be useful to report this in the general opcounters for backwards compatibility but to also break them out in an extended serverStatus version (with flag).



 Comments   
Comment by Greg Studer [ 02/May/14 ]

This is really just a request for more stats - which is tracked elsewhere.

Generated at Thu Feb 08 03:09:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.