This version of the documentation is archived and no longer supported.

Config Database

On this page

The config database supports sharded cluster operation. See the Sharding section of this manual for full documentation of sharded clusters.


The schema of the config database is internal and may change between releases of MongoDB. The config database is not a dependable API, and users should not write data to the config database in the course of normal operation or maintenance.

To access the config database, connect to a mongos instance in a sharded cluster, and use the following helper:

use config

You can return a list of the collections, with the following helper:

show collections

The config database is mainly for internal use, and during normal operations you should never manually insert or store data in it. However, if you need to verify the write availability of a config server, you can insert a document into a test collection (after making sure that no collection of that name already exists):


Modification of the config database on a functioning system may lead to instability or inconsistent data sets. If you must modify the config database, use mongodump to create a full backup of the config database.

db.testConfigServerWriteAvail.insert( { a : 1 } )

If the operation succeeds, the config server is available to process writes.

Future releases of the server may include different collections in the config database, so be careful when selecting a name for your test collection.



The changelog collection stores a document for each change to the metadata of a sharded collection.


The following example displays a single record of a chunk split from a changelog collection:

 "_id" : "<hostname>-<timestamp>-<increment>",
 "server" : "<hostname><:port>",
 "clientAddr" : "",
 "time" : ISODate("2012-12-11T14:09:21.039Z"),
 "what" : "split",
 "ns" : "<database>.<collection>",
 "details" : {
    "before" : {
       "min" : {
          "<database>" : { $minKey : 1 }
       "max" : {
          "<database>" : { $maxKey : 1 }
       "lastmod" : Timestamp(1000, 0),
       "lastmodEpoch" : ObjectId("000000000000000000000000")
    "left" : {
       "min" : {
          "<database>" : { $minKey : 1 }
       "max" : {
          "<database>" : "<value>"
       "lastmod" : Timestamp(1000, 1),
       "lastmodEpoch" : ObjectId(<...>)
    "right" : {
       "min" : {
          "<database>" : "<value>"
       "max" : {
          "<database>" : { $maxKey : 1 }
       "lastmod" : Timestamp(1000, 2),
       "lastmodEpoch" : ObjectId("<...>")

Each document in the changelog collection contains the following fields:


The value of changelog._id is: <hostname>-<timestamp>-<increment>.


The hostname of the server that holds this data.


A string that holds the address of the client, a mongos instance that initiates this change.


A ISODate timestamp that reflects when the change occurred.


Reflects the type of change recorded. Possible values are:

  • dropCollection
  • dropCollection.start
  • dropDatabase
  • dropDatabase.start
  • moveChunk.start
  • moveChunk.commit
  • split
  • multi-split

Namespace where the change occurred.


A document that contains additional details regarding the change. The structure of the details document depends on the type of change.


The chunks collection stores a document for each chunk in the cluster. Consider the following example of a document for a chunk named records.pets-animal_\"cat\":

   "_id" : "\"cat\"",
   "lastmod" : Timestamp(1000, 3),
   "lastmodEpoch" : ObjectId("5078407bd58b175c5c225fdc"),
   "ns" : "",
   "min" : {
         "animal" : "cat"
   "max" : {
         "animal" : "dog"
   "shard" : "shard0004"

These documents store the range of values for the shard key that describe the chunk in the min and max fields. Additionally the shard field identifies the shard in the cluster that “owns” the chunk.


The collections collection stores a document for each sharded collection in the cluster. Given a collection named pets in the records database, a document in the collections collection would resemble the following:

   "_id" : "records.pets",
   "lastmod" : ISODate("1970-01-16T15:00:58.107Z"),
   "dropped" : false,
   "key" : {
         "a" : 1
   "unique" : false,
   "lastmodEpoch" : ObjectId("5078407bd58b175c5c225fdc")

The databases collection stores a document for each database in the cluster. For each database, the corresponding document displays the name, the database’s primary shard, and the database’s sharding enabled status.

{ "_id" : "mydb", "primary" : "shard0000", "partitioned" : true }

The lockpings collection keeps track of the active components in the sharded cluster. Given a cluster with a mongos running on, the document in the lockpings collection would resemble:

{ "_id" : "", "ping" : ISODate("2012-10-12T18:32:54.892Z") }

The locks collection stores the distributed locks. The primary of the config server replica set takes a lock by inserting a document resembling the following into the locks collection.

   "_id" : "balancer",
   "state" : 2,
   "ts" : ObjectId("581178035b3b7dcb772022cd"),
   "who" : "ConfigServer:Balancer",
   "process" : "ConfigServer",
   "when" : ISODate("2016-10-27T03:44:03.007Z"),
   "why" : "CSRS Balancer"

Changed in version 3.4: As of version 3.4, the state field will always have a value 2 to prevent any legacy mongos instances from performing the balancing operation. The when field specifies the time when the config server member became the primary.


The mongos collection stores a document for each mongos instance affiliated with the cluster. mongos instances send pings to all members of the cluster every 30 seconds so the cluster can verify that the mongos is active. The ping field shows the time of the last ping, while the up field reports the uptime of the mongos as of the last ping. The cluster maintains this collection for reporting purposes.

The following document shows the status of the mongos running on

   "_id" : "",
   "ping" : ISODate("2019-09-25T22:48:34.062Z"),
   "up" : NumberLong(488),
   "waiting" : true,
   "mongoVersion" : "3.4.21",
   "advisoryHostFQDNs" : [

The settings collection holds the following sharding configuration settings:

The following is an example settings collection:

{ "_id" : "chunksize", "value" : 64 }
{ "_id" : "balancer", "stopped" : false, "mode" : "full" }
{ "_id" : "autosplit", "enabled" : true }

The shards collection represents each shard in the cluster in a separate document, as in the following:

{ "_id" : "shard0000", "host" : "localhost:30000", "state" : 1 }

If the shard is a replica set, the host field displays the name of the replica set, then a slash, then a comma-separated list of the hostnames of each member of the replica set, as in the following example:

{ "_id" : "shard0001", "host" : "shard0001/localhost:27018,localhost:27019,localhost:27020", "state" : 1 }

If the shard has zones assigned, this document has a tags field, that holds an array of the zones to which it is assigned, as in the following example:

{ "_id" : "shard0002", "host" : "localhost:30002", "state" : 1, "tags": [ "NYC" ] }

The tags collection holds documents for each zone range in the cluster. The documents in the tags collection resemble the following:

    "_id" : { "ns" : "records.users", "min" : { "zipcode" : "10001" } },
    "ns" : "records.users",
    "min" : { "zipcode" : "10001" },
    "max" : { "zipcode" : "10281" },
    "tag" : "NYC"

The version collection holds the current metadata version number. This collection contains only one document. For example:

{ "_id" : 1, "minCompatibleVersion" : 5, "currentVersion" : 6, "clusterId" : ObjectId("5d8beccf85e012bbe8d92fe6") }

To access the version collection you must use the db.getCollection() method. For example, to return the collection’s document: