[SERVER-76816] Improve StaleConfig exception handling in query Created: 03/May/23  Updated: 26/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Yuhong Zhang Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: PM-2144-QW-Fallout, oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-77207 Move sharding placement checks from o... Backlog
Assigned Teams:
Catalog and Routing
Participants:

 Description   

We have lots of repeated code in delete, update, and ts_modify stages handling the StaleConfig exception(here, here, and here). We would want to see if we can extract more common logics or absorb the exception handling into handlePlanStageYield().



 Comments   
Comment by Kaloian Manassiev [ 12/May/23 ]

Yes, this seems the right place to have it.

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