RoutingTableMissingMinKey
Description
Format
{    type: "RoutingTableMissingMinKey",    description: "<string>",    details: {       namespace: "<string>",       collectionUUID: <string>,       minKeyObj: { <document> },       globalMin: { <document> }    } } 
RoutingTableMissingMinKey inconsistency documents contain the following fields:
Field  | Type  | Description  | 
|---|---|---|
  | string  | Type of inconsistency document.  Returns a value of   | 
  | string  | Describes the nature of 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 minimum key used by the collection.  | 
  | document  | The expected minimum 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 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 }