-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
3
-
Not Needed
-
Iteration Brontosaurus, Iteration Citipati, Iteration Dreadnoughtus
In PM-3020 we added a new command checkMetadataConsistency that returns a cursor.
The command can be invoke at collection, database or cluster level and we should expose helpers for each level.
- Collection:
The command is invoked on "db" and the name of the collection is passed as command parameterdb.coll.checkMetadataConsistency(optionalOptions = {})
- Database:
The command is invoked on "db" and command parameter is either empty string "" or 1db.checkMetadataConsistency(optionalOptions = {})
- Cluster level
The command is invoked on "admin" database and command parameter is either empty string "" or 1
This level could be exposed either as sh function (I found this more intuitive):sh.checkClusterMetadataConsistency(optionaOptions = {})
Or we can reuse the database helper and call it on the "admin" database:
db.getSiblingDB('admin').checkMetadataConsistency(optionaOptions = {})
- depends on
-
NODE-5019 Expose an API to create a cursor from a command response
- Closed
- is caused by
-
COMPASS-6794 Investigate changes in PM-3020: Sharding metadata consistency check command
- Closed
- is depended on by
-
VSCODE-415 Support Scope: Sharding metadata consistency check command in mongosh
- Closed