[SERVER-47112] Improve setFeatureCompatibilityVersion 4.2 impact with many tables Created: 25/Mar/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dmitry Agranat | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
When a primary executes setFCV("4.2") its main work is to upgrade all its unique indexes to a new format ( When mongos executes setFCV, it sends it to the primary of the config replica set, which sends it to the primary of each shard, and waits for majority acknowledgement. |
| Comments |
| Comment by Connie Chen [ 26/Mar/20 ] |
|
rachelle.palmer will review to determine priority/what the acceptable impact should be? |