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

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

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • Admin, Sharding

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

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-5828 Metric/Stats Tracking

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-4868 Record more in config.changelog

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-7382 Track counters for each command

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              kbanker Kyle Banker
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: