[SERVER-31027] store UUID in routing table cache entries Created: 11/Sep/17 Updated: 06/Dec/22 Resolved: 25/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.12 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
This will definitely be required in 3.8 (or whenever we start routing requests by UUID), and there are already workarounds for change streams on sharded collections and mapReduce with sharded output to read the UUID directly from the config server, since it is not available on the routing table cache. If we can get this into an early dot release of 3.6, it would simplify some of those workarounds. |