RoutingTableMissingMaxKey
On this page
Description
Format
{ type: "RoutingTableMissingMaxKey", description: "<string>", details: { namespace: "<string>", collectionUUID: <string>, maxKeyObj: { <document> }, globalMax: { <document> } } }
RoutingTableMissingMaxKey
inconsistency documents contain the following fields:
Field | Type | Description |
---|---|---|
| string | Type of inconsistency document. Returns a value of |
| string | Describes the inconsistency found in the metadata. |
| document | Document with additional information on where the inconsistency exists in the database and sharded cluster. |
| string | Indicates the database and collection where the inconsistency exists. |
| UUID | UUID of the collection. |
| document | The max key used by the collection. |
| document | The expected max key of the collection. |
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 RoutingTableMissingMaxKey
inconsistency document:
{ cursor: { id: Long("0"), ns: "test.$cmd.aggregate", firstBatch: [ { type: "RoutingTableMissingMaxKey", description: "Routing table has a gap because last chunk boundary does not reach MaxKey", details: { namespace: "test.authors", collectionUUID: new UUID("62ebdb7e-a7bb-4151-a620-49d44cef097f"), maxKeyObj: { x: 0 }, globalMax: { x: MaxKey } } } ], }, ok: 1 }