Docs Menu
Docs Home
/
MongoDB Manual
/ / /

RoutingTableMissingMinKey

On this page

  • Description
  • Format
  • Example
RoutingTableMissingMinKey

A range gap exists in the routing table. The first chunk does not start from the minimum key value.

New in version 7.0.

{
type: "RoutingTableMissingMinKey",
description: "<string>",
details: {
namespace: "<string>",
collectionUUID: <string>,
minKeyObj: { <document> },
globalMin: { <document> }
}
}

RoutingTableMissingMinKey inconsistency documents contain the following fields:

Field
Type
Description
type
string

Type of inconsistency document. Returns a value of RoutingTableMissingMinKey for this inconsistency type.

description
string

Describes the nature of 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.

details.minKeyObj
document
The minimum key used by the collection.
details.globalMin
document
The expected minimum key of the collection.

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 RoutingTableMissingMinKey inconsistency document:

{
cursor: {
id: Long("0"),
ns: "test.$cmd.aggregate",
firstBatch: [
{
type: "RoutingTableMissingMinKey",
description: "Routing table has a gap because first chunk does not start from MinKey",
details: {
namespace: "test.authors",
collectionUUID: new UUID("62ebdb7e-a7bb-4151-a620-49d44cef097f"),
minKeyObj: {
x: 0
},
globalMin: {
x: MinKey
}
}
}
],
},
ok: 1
}
← RoutingTableMissingMaxKey