[COMPASS-6794] Investigate changes in PM-3020: Sharding metadata consistency check command Created: 05/May/23  Updated: 17/May/23  Resolved: 17/May/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
causes MONGOSH-1432 Create shell helpers for checkMetadat... Closed
Epic Link: COMPASS-5987
Documentation Changes: Not Needed

 Description   
Original Downstream Change Summary

Adding a new command to check for cluster wide sharding metadata consistency

Description of Linked Ticket

Epic Summary

Summary

We need a command or aggregation that users (and Atlas) can run to check that the collection metadata (e.g. UUIDs) is consistent across all shards.

Motivation

In the last months we have seen an increasing number of HELP tickets with the same issue: there was a sharded collection that had different UUID across shards. Usually, this sharded collection had different UUIDs because at some point the customer performed some operations directly against the shards, without going through a mongos. Despite the fact that PM-2689 will disallow direct operations against the shards, we see value in adding a way to verify that the collection metadata of a sharded collection is consistent across shards.

The reason why this issue is spotted since 5.0 is that on that version we introduced the renameCollection operation that verifies, before renaming the collection locally on a shard, that the local UUID matches the expected one.

Documentation

Product Description
Scope Document
Technical Design Document
Docs Update


Generated at Wed Feb 07 22:44:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.