[SERVER-40709] CatalogCache should mark database entry as needs refresh on encountering ShardNotFound when trying to get primary shard's Shard object Created: 18/Apr/19 Updated: 06/Dec/22 Resolved: 14/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | ShardingRoughEdges | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
This fixes a regression introduced in 4.0. However, a user should be running flushRouterConfig against all routers and shards after a dropDatabase or movePrimary, which would prevent this and other issues from occurring. |
| Comments |
| Comment by Matthew Saltz (Inactive) [ 14/Aug/19 ] |
|
Closing this ticket as Won't Fix, because per our documentation, users should be running _flushRouterConfig after movePrimary. |