[SERVER-76395] CheckMetadataConsistency should consider special collections Created: 21/Apr/23  Updated: 29/Oct/23  Resolved: 26/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc1

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Sharding EMEA 2023-05-01
Participants:
Linked BF Score: 0

 Description   

If CheckMetadataConsistency command is called on `config` database, it will report all local collections (e.g., config.cache.databases) as misplaced collection. Because it thinks they could only be placed in the config server, since it is the primary shard for the config database.

The command should take into account that those collections are special and can be present locally in all the shards without being sharded.



 Comments   
Comment by Githook User [ 28/Apr/23 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-76395 CheckMetadataConsistency should consider special collections

(cherry picked from commit e1f4b842e1e853729221f19ba3f98cb2f964a321)
Branch: v7.0
https://github.com/mongodb/mongo/commit/23953f2e332c2fcfb84a4b8d74800f2a2655fc5c

Comment by Githook User [ 26/Apr/23 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-76395 CheckMetadataConsistency should consider special collections
Branch: master
https://github.com/mongodb/mongo/commit/e1f4b842e1e853729221f19ba3f98cb2f964a321

Generated at Thu Feb 08 06:32:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.