Rethink CurOp/OpDebug modularization

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Once we have split the CurOp/OpDebug metrics into their own classes and files, we should revisit the modularization tags added in SERVER-111201.

      Ideally, most of the CurOp/OpDebug public methods will be able to be made private to the query module (the classes themselves and some functions, e.g. CurOp::get(), will have to remain public so that they can be accessed everywhere). Each metrics class/file can be assigned to the right module and (hopefully) be made module-private.

            Assignee:
            Unassigned
            Reporter:
            Alyssa Clark
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: