[SERVER-33401] Refuse to start up v4.0 shards if config.cache.collections or config.collections entries lack UUIDs Created: 20/Feb/18 Updated: 23/Feb/18 Resolved: 23/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Kaloian Manassiev |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 2018-03-12 | ||||||||
| Participants: | |||||||||
| Description |
|
Replication Change Streams relies on the presence of UUIDs, even though Sharding code doesn't yet rely on the presence of UUIDs. |
| Comments |
| Comment by Kaloian Manassiev [ 21/Feb/18 ] |
|
This ticket is related to The assignment of UUIDs on the per-shard cache collections will happen as part of |
| Comment by Dianna Hohensee (Inactive) [ 21/Feb/18 ] |
|
This may or may not require test work arounds due to |