drop¶

On this page

Behavior

drop¶

The drop command removes an entire collection from a database. The command has following syntax:

{ drop: <collection_name>, writeConcern: <document>}

The command takes the following fields:

Field Description

drop The name of the collection to drop.

writeConcern

Optional. A document expressing the write concern of the drop command. Omit to use the default write concern.

When issued on a sharded cluster, mongos converts the write concern of the drop command and its helper db.collection.drop() to "majority".

The mongo shell provides the equivalent helper method db.collection.drop().

Behavior¶

This command also removes any indexes associated with the dropped collection.

Starting in MongoDB 4.0.2, dropping a collection deletes its associated zone/tag ranges.

The drop command and its helper db.collection.drop() create an invalidate Event for any Change Streams opened on the dropped collection.

Resource Locking¶

Changed in version 4.2.

drop obtains an exclusive lock on the specified collection for the duration of the operation. All subsequent operations on the collection must wait until drop releases the lock.

Prior to MongoDB 4.2, drop obtained an exclusive lock on the parent database, blocking all operations on the database and all its collections until the operation completed.

← currentOp dropDatabase →