New in version 3.6.

The killAllSessions command kills all sessions for the specified users.


Killing a session kills any in-progress operations in the session, and closes any open cursors associated with these operations. The killed session may still be listed as a current session, and future operations may use the killed session.

{ killAllSessions: [ { user: <user>, db: <dbname> }, ... ]  }

The command takes an array of documents that specify the user and database name. Specify multiple array entries to kill sessions for multiple users. Specify an empty array to kill all sessions for all users in the system.

To run killAllSessions, use the db.runCommand( { <command> } ) method.

To view existing sessions, see $listSessions operation or $listLocalSessions.

Access Control

If the deployment enforces authentication/authorization, you must have the killAnySession to run the killAllSessions command.


Users can kill their own sessions even without killAnySession privilege action.


Kill All Sessions

The following operation kills all sessions for all users in the system:

db.runCommand( { killAllSessions: [ ] } )

Kill All Sessions for Specific Users

The following operation kills all sessions for the user appReader in the db1 and db2 databases:

db.runCommand( { killAllSessions: [ { user: "appReader", db: "db1" }, { user: "appReader", db: "db2" } ] } )