[SERVER-45576] Make explicit collection creation in sharding directly forward the create command to the primary shard again Created: 14/Jan/20  Updated: 29/Oct/23  Resolved: 31/Jan/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.4

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Mihai Andrei
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-45368 Allow collection and index creation i... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-01-27, Sharding 2020-02-10
Participants:

 Description   

The explicit create command on mongos was made to call _configsvrCreateCollection when we added the implicit collection creation loop through the config server under SERVER-32291.

To make it easier for the storage execution team to implement DDL in transactions, we should revert the create command behavior back to what it was before. At the moment, they are having trouble because the client's lsid, txnNumber is being propagated on _configsvrCreateCollection, which doesn't play well with the config server upconverting default writeConcern to majority, because writeConcern is not allowed on transaction statements besides commitTransaction.



 Comments   
Comment by Githook User [ 30/Jan/20 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com'}

Message: SERVER-45576 Make explicit collection creation in sharding directly forward the create command to the primary shard again
Branch: master
https://github.com/mongodb/mongo/commit/9a0ef61449aa413ff38f4bbd95e267558af4786a

Generated at Thu Feb 08 05:09:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.