Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
ALL
-
-
Sharding 2021-03-22, Sharding 2021-04-05, Sharding EMEA 2021-05-03
-
39
-
1
Description
For some reason, the ShardInvalidatedForTargeting exception is being propagated back to the client as a write error rather than being automatically retried by mongos.
bool allowLocks = true; |
auto tempNssRoutingInfo = Grid::get(opCtx)->catalogCache()->getCollectionRoutingInfo(
|
opCtx,
|
constructTemporaryReshardingNss(sourceNss.db(), getCollectionUuid(opCtx, sourceNss)),
|
allowLocks);
|
|
|
uassert(ShardInvalidatedForTargetingInfo(sourceNss),
|
"Routing information is not available for the temporary resharding collection.", |
tempNssRoutingInfo.getStatus() != ErrorCodes::StaleShardVersion);
|
|
|
uassertStatusOK(tempNssRoutingInfo);
|
Attachments
Issue Links
- related to
-
SERVER-81508 Potential double-execution of write statements when ShardCannotRefreshDueToLocksHeld is thrown
-
- Closed
-