Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Operating System:
ALL
Sprint:
CAR Team 2024-04-29, CAR Team 2024-05-13
Linked BF Score:
200
Story Points:
2
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

A direct connection to a shard could fail with staleConfig after ~~SERVER-80135~~ since shardCollection information refresh has been converted from sync to async. If a direct connection ends up using stale information, the command fails with the sharding status of collection XYZ Is not currently known and needs to be recovered.

The fix is to not use the direct connection, or do something before to force a refresh.

related to

SERVER-89252 Ban `lookup_targeting.js` to run in `sharding_csrs_continuous_config_stepdown` suite

Closed

SERVER-89548 covered_shardkey_indexes.js test assumes coll metadata is always known on shard

Closed

SERVER-89931 StaleConfig error is not retried as a first statement in a txn with FLE sharded collections

Closed

Assignee:: Pol Pinol
Reporter:: Sulabh Mahajan
Participants:: Pol Pinol, Sulabh Mahajan
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Apr 22 2024 02:31:50 PM UTC
Updated:: Apr 29 2024 01:50:35 PM UTC
Resolved:: Apr 29 2024 01:48:35 PM UTC
Confidence Status Last Update:: 26/Apr/24 9:59 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates