VOOZH about

URL: https://www.mongodb.com/docs/atlas/unsupported-commands/

⇱ Unsupported Commands in Atlas - Atlas - MongoDB Docs

For AI agents: a documentation index is available at https://www.mongodb.com/docs/llms.txt — markdown versions of all pages are available by appending .md to any URL path.
Docs Menu

Unsupported Commands in Atlas

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

  • Doesn't support the $where operator.

  • Limits the count operation on the local database to the system.replset and oplog.rs collections.

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

To learn more, see Operational Limits.

Doesn't support $where operator.

  • 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" }

Limits execution to these two documents:

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

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

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

Doesn't support the $$USER_ROLES system variable.

Doesn't support the $$USER_ROLES system variable.

Doesn't support the $$USER_ROLES system variable.

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.

Unsupported Command Line Options

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

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.

Limited Commands

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

Atlas supports the following sharding command on only M30+ sharded clusters:

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

Sessions

Commands
Shell Method
Privilege Actions

Replication

Sharding

[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.

[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.

Contact Support

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