[SERVER-75165] checkMetadataConsistency improperly access sharded coll info Created: 23/Mar/23  Updated: 29/Oct/23  Resolved: 27/Mar/23

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

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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-04-03
Participants:

 Description   

When redacting a UUIDMismatchInconsistency we also attach the information weather the shard thinks the collection is sharded. This information is wrong an it will always be false. In fact it is taken from a CollectionPtr that is constructed using the default constructor that doesn't set the internal CollectionPtr::_shardKeyPattern.



 Comments   
Comment by Githook User [ 27/Mar/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-75165 checkMetadataConsistency improperly access sharded coll info
Branch: master
https://github.com/mongodb/mongo/commit/fae11c80096602447cea7be65c229e6ab331ec59

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