MissingRoutingTable
On this page
Description
Format
{ type: "MissingRoutingTable", description: "<string>", details: { namespace: "<string>", collectionUUID <uuid> } }
MissingRoutingTable
inconsistency documents contain the following fields:
Field | Type | Description |
---|---|---|
type | string | Type of inconsistency document. Returns a value of |
description | string | Describes the inconsistency found in the metadata. |
details | document | Document with additional information on where the inconsistency exists in the database and sharded cluster. |
details.namespace | string | Indicates the database and collection where the inconsistency exists. |
details.collectionUUID | UUID | UUID of the collection without the routing table. |
Example
Use the db.adminCommand()
method to call the
checkMetadataConsistency
command:
db.adminCommand( { checkMetadataConsistency: 1 } )
The method returns a cursor with a batch of documents showing the inconsistencies
found in the sharding metadata. The example below shows a cursor with
a MissingRoutingTable
inconsistency document:
{ cursor: { id: Long("0"), ns: "test.$cmd.aggregate", firstBatch: [ { type: "MissingRoutingTable", description: "There is a sharded collection without routing table", details: { namespace: "test.authors", collectionUUID: new UUID("1ad56770-61e2-48e9-83c6-8ecefe73cfc4") } } ], }, ok: 1 }