[SERVER-40333] Only clone collection options once for each shard on shard collection Created: 25/Mar/19  Updated: 29/Oct/23  Resolved: 26/Mar/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.0.6, 4.1.9
Fix Version/s: 4.0.9, 4.1.10

Type: Improvement Priority: Major - P3
Reporter: Blake Oler Assignee: Blake Oler
Resolution: Fixed Votes: 1
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Sharding 2019-04-08
Participants:
Case:

 Description   

In current sharding code, we make a request to clone a collection's options once for each chunk, regardless of number of shards. This generates duplicate work – we should only need to do this once for each unique shard.



 Comments   
Comment by Kelsey Schubert [ 05/Apr/19 ]

This change gains back performance of shardCollection in 4.0 as compared to 3.6.

Comment by Githook User [ 01/Apr/19 ]

Author:

{'email': 'blake.oler@mongodb.com', 'name': 'Blake Oler', 'username': 'BlakeIsBlake'}

Message: SERVER-40333 Only clone collection options once for each shard in shardsvrShardCollection
Branch: v4.0
https://github.com/mongodb/mongo/commit/029336d07dd89eee17cfa090ca0b63f44883b485

Comment by Githook User [ 26/Mar/19 ]

Author:

{'email': 'blake.oler@mongodb.com', 'name': 'Blake Oler', 'username': 'BlakeIsBlake'}

Message: SERVER-40333 Only clone collection options once for each shard in shardsvrShardCollection
Branch: master
https://github.com/mongodb/mongo/commit/8a19243db63197056d6230daa92cf54a847912e4

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