Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-5787

Track opcounters (insert/delete/update) which results from sharding commands

XMLWordPrintableJSON

    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      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).

            Assignee:
            Unassigned Unassigned
            Reporter:
            kbanker Kyle Banker (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: