[SERVER-44105] Perform ShardServerCatalogLoader writes in a single transaction Created: 18/Oct/19  Updated: 06/Dec/22  Resolved: 18/Feb/22

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-42737 MongoDB stuck on update metadata Closed
related to SERVER-48566 Shard loader in primary nodes blindly... Closed
related to SERVER-38341 Remove Parallel Batch Writer Mutex Closed
related to SERVER-63847 Complete TODO listed in SERVER-44105 Closed
Assigned Teams:
Sharding EMEA
Operating System: ALL
Participants:
Case:

 Description   

And this should remove the need to set the refresh flag in config.cache.collections. Most likely will need to keep the secondary read logic around for backwards compatibility with v4.2.



 Comments   
Comment by Githook User [ 20/Sep/22 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-63847 Complete TODO listed in SERVER-44105
Branch: master
https://github.com/mongodb/mongo/commit/05a9613d1ca645467dd98b915b3ffd0a4a84e9dc

Comment by Louis Williams [ 29/Sep/20 ]

I think there's a way we can complete the desired work in SERVER-38341 without this change, if necessary.

Comment by Ratika Gandhi [ 16/Mar/20 ]

cc. kaloian.manassiev

Comment by Connie Chen [ 16/Mar/20 ]

ratika.gandhi just flagging this to be prioritized, once this is complete Execution can begin work on SERVER-38341

Comment by Judah Schvimer [ 16/Dec/19 ]

SERVER-38341 would be a big win. Implementing this early enough for SERVER-38341 to land in 4.4 would be really helpful.

Comment by Randolph Tan [ 22/Nov/19 ]

SERVER-38341 depends on this as it will nullify the fix in SERVER-42737

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