[SERVER-32622] Upgrade work for track unsharded collections Created: 09/Jan/18 Updated: 06/Dec/22 Resolved: 09/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.7.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
On setFCV=3.8 on the config server, after all the shards are in fcv=3.8, the config server will call listCollections on each database’s primary shard and create an entry in the sharding catalog for each unsharded collection and views. It will also make sure that if the primary shard doesn't own a chunk for a sharded collection, it should have the indexes and matching collection options with another shard that has chunks. |