Sharded Node Direct Commands

Starting in MongoDB 8.0, these are the only commands you can run directly on a node in a sharded cluster. You can also run a shell helper directly on a node if it calls one of the supported commands. For certain collections on the admin database, the local database, or the config database, you can run read and aggregation operations directly on a node. To learn more, see Single-Shard Collection Reads.

Note

The list might not be exhaustive [1].

Command	Available Helper Methods
`abortTransaction`	`Session.abortTransaction()`
`appendOplogNote`
`authenticate`	`passwordPrompt()`
`autoCompact`
`buildInfo`
`commitTransaction`	`Session.commitTransaction()` `Session.withTransaction()`
`compact`
`connectionStatus`
`connPoolStats`
`createRole`	`db.createRole()`
`createUser`	`db.createUser()`
`currentOp`	`db.currentOp()`
`dbHash` (Added in 8.0.5)
`dropAllRolesFromDatabase`	`db.dropAllRoles()`
`dropAllUsersFromDatabase`	`db.dropAllUsers()`
`dropRole`	`db.dropRole()`
`dropUser`	`db.dropUser()`
`endSessions`
`flushRouterConfig`
`fsync`	`db.fsyncLock()`
`fsyncUnlock`	`db.fsyncUnlock()`
`getAuditConfig`
`getClusterParameter`
`getCmdLineOpts`
`getLog`
`getParameter`
`getShardMap`
`grantPrivilegesToRole`	`db.grantPrivilegesToRole()`
`grantRolesToRole`	`db.grantRolesToRole()`
`grantRolesToUser`	`db.grantRolesToUser()`
`hello`
`hostInfo`
`invalidateUserCache`
`killAllSessions`
`killAllSessionsByPattern`
`killCursors`
`killOp`
`killSessions`
`listCommands`
`lockInfo`
`logApplicationMessage`
`logout`
`logRotate`
`ping`
`profile`	`db.setProfilingLevel()`
`replSetAbortPrimaryCatchUp`
`replSetFreeze`	`rs.freeze()`
`replSetGetConfig`	`rs.conf()`
`replSetGetStatus`	`rs.status()`
`replSetMaintenance`
`replSetReconfig`	`rs.reconfig()`
`replSetResizeOplog`
`replSetStepDown`	`rs.stepDown()`
`replSetSyncFrom`	`rs.syncFrom()`
`revokePrivilegesFromRole`	`db.revokePrivilegesFromRole()`
`revokeRolesFromRole`	`db.revokeRolesFromRole()`
`revokeRolesFromUser`	`db.revokeRolesFromUser()`
`rolesInfo`
`rotateCertificates`
`serverStatus`
`setParameter`
`shardingState`
`startSession`	`Mongo.startSession()`
`top`
`updateRole`	`db.updateRole()`
`updateUser`	`db.changeUserPassword()`
`usersInfo`
`whatsmyuri`

[1]	Specific command documentation can include compatibility info.

Single-Shard Collection Reads

You can run read and aggregation operations directly on a node for databases and collections that always reside entirely on one shard. These include collections in the admin database, local, and config databases.

The following collections are exceptions. You cannot read these collections directly on a node. You must connect to mongos instead:

Important

The contents and schema of the collections in the admin, local, and config databases are internal to MongoDB and can change at any time. If your application depends on the data in these collections, it can stop working after an upgrade.

To learn more about the collections in the config database, see Config Database.

Back

Troubleshoot Sharded Clusters

Storage Engines