[SERVER-58373] Stop forcing routing info refresh in cluster split command Created: 08/Jul/21  Updated: 14/Sep/23  Resolved: 12/Nov/21

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

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

Issue Links:
Related
related to SERVER-81080 rename OplogDeleteEntryArgs::oplogSlo... Closed
Assigned Teams:
Sharding EMEA
Operating System: ALL
Participants:

 Description   

Rather than forcing a routing info refresh at the very beginning of cluster split command we should rely on the shard versioning protocol that will ensure that eventually the request will be routed to the correct shard.


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