[SERVER-5324] RunOnAllShards commands need to use newer command stale config retry logic Created: 16/Mar/12  Updated: 06/Dec/22  Resolved: 31/Oct/19

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

Type: Bug Priority: Minor - P4
Reporter: Greg Studer Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-7210 Consolidate internal mongos interfaces Closed
Assigned Teams:
Sharding
Operating System: ALL
Sprint: Sharding 16 (06/24/16), Sharding 17 (07/15/16), Sharding 18 (08/05/16)
Participants:
Case:

 Description   

...which is built into the newer logic in strategy_shard::commandOp().

Otherwise the older retry logic can throw exceptions in rare cases.



 Comments   
Comment by Randolph Tan [ 28/Jul/16 ]

Looks like we should be able to convert existing RunOnAllShards to Strategy::commandOp by passing an empty BSON on targettingQuery.

Comment by Greg Studer [ 16/Mar/12 ]

Related to general refactoring of other sharded command logic.

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