[SERVER-39450] setFCV from 4.0 to 4.2 blocks while background index builds are running Created: 08/Feb/19 Updated: 06/Dec/22 Resolved: 14/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
In order to update unique index catalog data, setFCV runs a special collMod for each unique index and waits for those to be majority committed. The collMod command itself cannot run while background index builds are in progress on the same collection, therefore the setFCV command will return an error (on a primary) or wait until all index builds are done, blocking replication (on a secondary). We should investigate ways of mitigating this behavior. |
| Comments |
| Comment by Geert Bosch [ 14/Feb/19 ] |
|
This is similar to the situation for upgrade from 3.4 to 3.6 where we use collMod to add UUIDs. So we don't believe this will be an issue. |