[SERVER-66700] Port runCommandWithFixedRetryAttempts() to DBDirectClientWrapper Created: 23/May/22  Updated: 27/Oct/23  Resolved: 09/Feb/23

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: [DO NOT USE] Backlog - Sharding NYC
Resolution: Gone away 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-66711 Get rid of ShardLocal Closed
Assigned Teams:
Sharding NYC
Participants:
Story Points: 4

 Description   

See SERVER-66674 for more context. Our goal is to relocate the mutations on Config server using runCommandWithFixedRetryAttempts() to DBDirectClientWrapper.

Note: unlike the parent ticket, not all invocations of runCommandWithFixedRetryAttempts() are specific to the config server, but most of them are. There are ~75 total call sites. One example when this command is applied to a different shard is sendWriteCommandToRecipient(). We also need to exclude cases when the call may be from a normal shard to the config shard, however that would be very odd.

To verify the conversion is correct add the invariant that when this is invoked on new direct client wrapper, the cluster role should be config server - this needs to be verified in normal mode, not as Catalog shard. If some cases are not obvious, create another ticket.



 Comments   
Comment by Jack Mulrow [ 09/Feb/23 ]

The design for PM-2290 has changed to no longer include removing ShardLocal, which this ticket assumed, so closing as gone away.

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