[SERVER-38185] _shardsvrShardCollection does not always include collectionUUID in the response Created: 16/Nov/18  Updated: 29/Oct/23  Resolved: 27/Feb/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.1.5
Fix Version/s: 4.1.9

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Sharding 2018-12-31, Sharding 2019-01-14, Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11
Participants:
Linked BF Score: 69

 Description   

For example, if the command was "joined" here:

https://github.com/mongodb/mongo/blob/r4.1.5/src/mongo/db/s/shardsvr_shard_collection.cpp#L604

Need to also audit what happens when the command is retried, but fell into the else branch instead of joining like in the above link

the configsvr/shard/mongos versions of shard collection should probably assert that uuid field always exists



 Comments   
Comment by Githook User [ 27/Feb/19 ]

Author:

{'name': 'jannaerin', 'username': 'jannaerin', 'email': 'golden.janna@gmail.com'}

Message: SERVER-38185 _shardsvrShardCollection should return uuid when joining an existing shardCollection
Branch: master
https://github.com/mongodb/mongo/commit/beaa1e7ee2fa2dc519d0302915eaf6c36cdd61c2

Generated at Thu Feb 08 04:48:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.