ZonesRangeOverlap
On this page
Description
Format
{ type: "ZonesRangeOverlap", description: "<string>", details: { namespace: "<string>", collectionUUID: <string>, zoneA: {<document>}, zoneB: {<document>} } }
ZonesRangeOverlap
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 first zone that overlaps with the second zone. |
| document | The second zone that overlaps with the first zone. |
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 ZonesRangeOverlap
inconsistency document:
{ cursor: { id: Long("0"), ns: "test.$cmd.aggregate", firstBatch: [ { type: "ZonesRangeOverlap", description: "Found two overlapping zones", details: { namespace: "test.authors", collectionUUID: new UUID("62ebdb7e-a7bb-4151-a620-49d44cef097f"), zoneA: { ns: "test.authors", tag: "64ddec77e0d32b766bb8d5fe", min: { x: MinKey }, max: { x: 0 } }, zoneB: { ns: "test.authors", tag: "64ddec77e0d32b766bb8d5ff", min: { x: -10 }, max: { x: MaxKey } } } } ], }, ok: 1 }