/ /

Unsupported Commands in Atlas Clusters

Unsupported Commands in M0 and Atlas Flex Clusters

Atlas Free clusters and Flex clusters don't support all functionality available to other clusters. To learn more about M0 cluster limits, see Atlas Free Cluster Limits. To learn more about Flex cluster limits, see Atlas Flex Limitations.

Note

If you use an unsupported command or invalid syntax, Atlas returns the following error message:

 <$command> is not allowed or the syntax is incorrect,
 see the Atlas documentation for more information.

To learn more about valid syntax, see Database Commands

Limited Commands

You can run the following commands with limits in Free clusters and Flex clusters:

Command

Limit

aggregate

Limits the maxTimeMs parameter to 300 seconds (300000).
Ignores the allowDiskUse parameter.
Doesn't support $accumulator and $function operators.
Doesn't support the $$USER_ROLES system variable.

count

Doesn't support the $where operator.
Limits the count operation on the local database to the system.replset and oplog.rs collections.

dbStats

Free clusters and Flex clusters don't allow the dbStats command on the local and config databases.

To learn more, see Operational Limits.

distinct

Doesn't support $where operator.

find

Doesn't support the $where operator.
Doesn't support the $$USER_ROLES system variable.
Ignores the allowDiskUse parameter.
Limits the find operation on the local database to the oplog.rs collection.
Limits the find operation to using an equality condition when querying the ns field in the oplog.rs collection on the local database.
{ "ns" : "test.foo" }

getParameter

Limits execution to these two documents:

{ "getParameter": 1, "authSchemaVersion": 1 }
{ "getParameter": 1, "authenticationMechanisms": 1 }

db.killOp()

Limits the db.killOp() method to the MongoDB user who ran the operation.

collection.updateOne()

Doesn't support the $$USER_ROLES system variable.

collection.updateMany()

Doesn't support the $$USER_ROLES system variable.

findAndModify

Doesn't support the $$USER_ROLES system variable.

serverStatus

Limits response to the following fields:

$clusterTime.clusterTime
$clusterTime.operationTime
$clusterTime.signature.hash
$clusterTime.signature.keyId
$clusterTime.signature
asserts.msg
asserts.regular
asserts.rollovers
asserts.user
asserts.warning
atlasVersion.gitVersion
atlasVersion.version
connections.available
connections.current
connections.totalCreated
extra_info.note
extra_info.page_faults
host
localTime
mem.bits
mem.mapped
mem.mappedWithJournal
mem.resident
mem.supported
mem.virtual
metrics.atlas.bytesInWrites
metrics.atlas.connectionPool.totalCreated
network.bytesIn
network.bytesOut
network.numRequests
ok
opcounters.command
opcounters.delete
opcounters.getmore
opcounters.insert
opcounters.query
opcounters.update
opcountersRepl.command
opcountersRepl.delete

opcountersRepl.getmore
opcountersRepl.insert
opcountersRepl.query
opcountersRepl.update
pid
process
repl.electionId
repl.hosts[]
repl.ismaster
repl.lastWrite.lastWriteDate
repl.lastWrite.majorityOpTime.t
repl.lastWrite.majorityOpTime.ts
repl.lastWrite.majorityWriteDate
repl.lastWrite.opTime.t
repl.lastWrite.opTime.ts
repl.me
repl.primary
repl.rbid
repl.secondary
repl.setName
repl.setVersion
repl.tags.nodeType
repl.tags.provider
repl.tags.region
repl.tags
storageEngine.backupCursorOpen
storageEngine.dropPendingIdents
storageEngine.name
storageEngine.oldestRequiredTimestampForCrashRecovery
storageEngine.persistent
storageEngine.readOnly
storageEngine.supportsCommittedReads
storageEngine.supportsPendingDrops
storageEngine.supportsSnapshotReadConcern
uptime
uptimeEstimate
uptimeMillis
version

Unsupported Commands

Free clusters and Flex clusters don't support the following commands:

Note

The commands available for clusters of all other tiers, M10 and larger, correspond to the privileges defined for the built-in Atlas MongoDB roles. To learn more about permissions, see Atlas User Privileges.

_migrateClone
_recvChunkAbort
_recvChunkCommit
_recvChunkStart
_recvChunkStatus
_transferMods
appendOplogNote
applyOps
authenticate
autoCompact
authSchemaUpgrade
cleanupOrphaned
cloneCollection
cloneCollectionAsCapped
compact
copydbgetnonce
copydbsaslstart
createRole
db.collection.getSearchIndexes()
createUser
currentOpCtx
dataSize
dbHash
dropAllRolesFromDatabase
dropAllUsersFromDatabase
dropConnections
dropRole
enableFreeMonitoring
forcerror
fsync
fsyncUnlock

getDiagnosticData
getPrevError
getShardMap
grantPrivilegesToRole
grantRolesToRole
grantRolesToUser
handshake
hostInfo
invalidateUserCache
killAllSessions
killAllSessionsByPattern
killAnySession
killSessions
$listLocalSessions
$listSessions
lockInfo
logRotate
logApplicationMessage
shardedFinish
mapReduce
planCacheClear
planCacheClearFilters
planCacheListFilters
planCacheListPlans
planCacheListQueryShapes
$planCacheStats aggregation pipeline stage
planCacheSetFilter
$querySettings aggregation pipeline stage
reIndex
removeQuerySettings
repairCursor
repairDatabase

Unsupported Command Line Options

Free clusters and Flex clusters don't support the following command line tool options:

Command Line Tool	Unsupported Options
`mongorestore`	--restoreDbUsersAndRoles --oplogReplay --preserveUUID
`mongodump`	--dumpDbUsersAndRoles --oplog

For more information, see M0 Cluster Limits.

Unsupported Commands in M10+ Clusters

Atlas requires clients to authenticate to access an Atlas cluster. Atlas provides a curated list of Database User Privileges. These privileges provide access to a subset of MongoDB commands.

The commands in this section are unsupported in both Atlas Core clusters and Atlas Infinite clusters. Atlas Infinite clusters don't support some additional commands. To learn more, see Unsupported Commands in Atlas Infinite M10+ Clusters.

Limited Commands

Atlas limits the db.killOp() method to the MongoDB user who ran the operation.

Atlas doesn't support the killAllSessions command unless the database user has:

the killAnySession privilege, or
the killOpSession role.

Atlas supports the following sharding command on only M30+ sharded Atlas Core clusters. Atlas Infinite clusters do not support sharded clusters in public preview, so these commands do not apply to Atlas Infinite clusters.

Command	Shell Method	Privilege Action
`abortRewriteCollection`		`rewriteCollection`
`reshardCollection`	`sh.reshardCollection()`	`reshardCollection`
`rewriteCollection`		`rewriteCollection`
`unshardCollection`	`sh.unshardCollection()`	`unshardCollection`

Unsupported Commands

The following table lists the most common commands and shell methods that database user privileges do not support. To ensure cluster stability and performance, Atlas subsumes or restricts the functionality that these commands provide.

Administrative

Commands	Shell Method	Privilege Actions
`applyOps`
`dropConnections`		`dropConnections`
`eval`	`db.eval()`
`fsync`	`db.fsyncLock()`	`fsync`
`fsyncUnlock`	`db.fsyncUnlock()`	`unlock`
`getAuditConfig`
`logApplicationMessage`		`applicationMessage`
`logRotate`		`logRotate`
`reIndex`		`reIndex`
`rotateCertificates`		`rotateCertificates`
`setAuditConfig`
`setClusterParameter`
`setDefaultRWConcern`		`setDefaultRWConcern`
`setFeatureCompatibilityVersion`
`setParameter`	`db.setLogLevel()` Others that use `setParameter`.	`setParameter`
`shutdown`	`db.shutdownServer()`	`shutdown`

Replication

Commands	Shell Method	Privilege Actions
`replSetFreeze`	`rs.freeze()`	`replSetStateChange`
`replSetGetRBID`
`replSetInitiate`	`rs.initiate()`
`replSetMaintenance`		`replSetStateChange`
`replSetReconfig`	`rs.reconfig()`
`replSetResizeOplog`
`replSetRequestVotes`
`replSetStepDown`	`rs.stepDown()`	`replSetStateChange`
`replSetSyncFrom`	`rs.syncFrom()`	`replSetStateChange`
`resync`		`resync`

Sharding

Commands	Shell Method	Privilege Actions
	`sh.disableBalancing()` [1]
	`sh.enableBalancing()` [1]
`refineCollectionShardKey` [2]		`refineCollectionShardKey`
`removeShard`		`removeShard`

[1]	(1, 2) You can use `setAllowMigrations` to control the balancing of a specific collection.

[2]	This command is not supported on global write clusters only.

User and Role Management

Note

As an alternative, see the available Atlas User Roles.

Commands	Shell Method	Privilege Actions
`createRole`	`db.createRole()`	`createRole`
`createUser`	`db.createUser()`	`createUser`
`dropAllRolesFromDatabase`	`db.dropAllRoles()`	`dropRole`
`dropAllUsersFromDatabase`	`db.dropAllUsers()`	`dropUser`
`dropRole`	`db.dropRole()`	`dropRole`
`dropUser`	`db.dropUser()`	`dropUser`
`getUser` [3]	`db.getUser()` and `db.getUsers()` [3]
`grantRolesToUser`	`db.grantRolesToUser()`	`grantRole`
`invalidateUserCache`		`invalidateUserCache`
`revokePrivilegesFromRole`	`db.revokePrivilegesFromRole()`	`revokeRole`
`revokeRolesFromRole`	`db.revokeRolesFromRole()`	`revokeRole`
`revokeRolesFromUser`	`db.revokeRolesFromUser()`	`revokeRole`
`updateRole`	`db.updateRole()`
`updateUser`	`db.updateUser()`
`usersInfo`

[3]	(1, 2) You can call `getUser` for your own user account.

Unsupported Command Line Options

M10+ clusters don't support the --preserveUUID option for mongorestore.

Unsupported Commands in Atlas Infinite M10+ Clusters

In addition to the commands that M10+ clusters don't support, Atlas Infinite clusters don't support the following functionality or commands.

Limited Commands

Atlas Infinite clusters only support the profile command when the database profiler level is 0.

Unsupported Commands

Atlas Infinite clusters don't support the following commands. On Atlas Core clusters, you can run these commands with the corresponding privilege action.

Commands	Shell Method	Privilege Actions
`abortRewriteCollection`		`rewriteCollection`
`autoCompact`		`compact`
`compact`		`compact`
`dbHash`		`dbHash`
`reshardCollection`	`sh.reshardCollection()`	`reshardCollection`
`rewriteCollection`		`rewriteCollection`
`setIndexCommitQuorum`
`unshardCollection`	`sh.unshardCollection()`	`unshardCollection`

Contact Support

Contact Atlas support if your use case requires access to a command that the Atlas database user privileges don't currently support.

Back

Free Cluster Limits

Supported Commands