[SERVER-67127] Delete shell logic to fall back to currentOp command rather than $currentOp stage Created: 08/Jun/22  Updated: 29/Oct/23  Resolved: 22/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: David Storch Assignee: David Storch
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by COMPASS-6043 Investigate changes in SERVER-67127: ... Closed
Related
Backwards Compatibility: Minor Change
Sprint: QE 2022-07-11, QE 2022-07-25, QE 2022-08-08, QE 2022-08-22
Participants:

 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.



 Comments   
Comment by Githook User [ 22/Aug/22 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}

Message: SERVER-67127 Delete 'db.currentOpLegacy()' helper
Branch: master
https://github.com/mongodb/mongo/commit/b324e20468ca7d2c3afd3cfa57f1ba38c77a3655

Generated at Thu Feb 08 06:07:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.