Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-6043

Investigate changes in SERVER-67127: Delete shell logic to fall back to currentOp command rather than $currentOp stage

    XMLWordPrintableJSON

Details

    • Icon: Investigation Investigation
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • No version
    • None
    • None
    • None
    • Not Needed

    Description

      Original Downstream Change Summary

      This ticket removes support for the `db.currentOP()` helper from the legacy shell. This was an alias for `db.currentOp()` that appeared to be unused in the server code base. Uses of `db.currentOP()` outside of the server code base which could run inside the 6.1+ legacy mongo shell should be changed to `db.currentOp()`.

      Description of Linked Ticket

      The shell's currentOp() helper has some logic to fallback to the old currentOp command rather than the $currentOp aggregation stage when it is connected to the Atlas Proxy:

      https://github.com/mongodb/mongo/blob/3a49875934cfd7e70d789b4ad7093286d189acc9/src/mongo/shell/db.js#L810-L815

      It's possible that this fallback logic is safe to delete, though we should check with the knowledgeable folks on the Cloud team. My thinking is that since new versions of the shell are no longer shipped to users, this fallback logic should be ok to get rid of. We don't need it in the server's testing environment (because we don't test the Atlas Proxy in this environment), and the current remaining purpose of the mongo shell is to act as the testing harness for the server.

      Attachments

        Activity

          People

            Unassigned Unassigned
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: