Docs Menu

Docs HomeDevelop ApplicationsMongoDB Manual

ZonesRangeOverlap

On this page

  • Description
  • Format
  • Example
ZonesRangeOverlap

Overlapping zones exist for the same collection.

New in version 7.0.

{
type: "ZonesRangeOverlap",
description: "<string>",
details: {
namespace: "<string>",
collectionUUID: <string>,
zoneA: {<document>},
zoneB: {<document>}
}
}

ZonesRangeOverlap inconsistency documents contain the following fields:

Field
Type
Description
type
string

Type of inconsistency document. Returns a value of ZonesRangeOverlap 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.zoneA
document
The first zone that overlaps with the second zone.
details.zoneB
document
The second zone that overlaps with the first zone.

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
}
← ShardThinksCollectionIsUnsharded