CollectionUUIDMismatch
Description
CollectionUUIDMismatchA collection exists on a shard with a locally registered UUID that differs from the one registered in the
config.collectionscluster catalog.New in version 7.0.
Format
{    type: "CollectionUUIDMismatch",    description: "<string>",    details: {       namespace: "<string>",       shard: "<string>",       localUUID: UUID("<uuid>"),       uuid: UUID("<uuid>")    } } 
CollectionUUIDMismatch 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.  | 
  | string  | The shard where the inconsistency exists.  | 
  | UUID  | The UUID registered locally on the shard.  | 
  | UUID  | The UUID of the collection found in the   | 
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 CollectionUUIDMismatch inconsistency document:
{    cursor: {       id: Long("0"),       ns: "test.$cmd.aggregate",       firstBatch: [          {             type: "CollectionUUIIDMismatch",             description: "Found collection on non primary shard with mismatching UUID",             details: {                namespace: "test.authors",                shard: "shard02",                localUUID: new UUID("1ad56770-61e2-48e9-83c6-8ecefe73cfc4"),                uuid: new UUID("a3153e8a-3544-43ec-928f-37f72b48dee9")             }          }       ],    },    ok: 1 }