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

Delete shell logic to fall back to currentOp command rather than $currentOp stage

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.1.0-rc0
    • None
    • None
    • None
    • Minor Change
    • QE 2022-07-11, QE 2022-07-25, QE 2022-08-08, QE 2022-08-22

    Description

      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

            david.storch@mongodb.com David Storch
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: