[SERVER-66674] Get rid of all calls runBatchWriteCommand() on config Shard instance Created: 23/May/22  Updated: 29/Oct/23  Resolved: 04/Oct/22

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

Type: Improvement Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Andrew Shuvalov (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-66672 Support the runBatchWriteCommand on S... Closed
is depended on by SERVER-66911 Get rid of Shard::_exhaustiveFindOnCo... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2022-05-30, Sharding NYC 2022-06-13, Sharding 2022-06-27, Sharding 2022-07-11, Sharding 2022-07-25, Sharding 2022-08-08, Sharding 2022-08-22, Sharding 2022-09-05, Sharding 2022-09-19, Sharding 2022-10-03, Sharding 2022-10-17
Participants:
Story Points: 3

 Description   

This requires SERVER-66672 to be complete first. There are few invocations of 
runBatchWriteCommand() on config shard outside of ShardingCatalogClientImpl, for example in SetAllowMigrationsCoordinator. Get rid of them and replace with helper from the previous ticket.
 
Then remove the runBatchWriteCommand() method from Shard interface completely.


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