[SERVER-45374] Unique index that gets rebuilt as part of startup recovery/repair is using data format version as 6 or 8 and NOT 11 or 12. Created: 06/Jan/20 Updated: 29/Oct/23 Resolved: 24/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.4, 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Execution Team 2020-01-27 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 44 | ||||||||||||||||
| Description |
|
Unique index rebuilt as part of mongodb 4.2 startup repair/recovery will have either kDataFormatV2KeyStringV1IndexVersionV2 (8) or kDataFormatV1KeyStringV0IndexVersionV1 (6) since FCV is uninitialized at that point of time. To be noted, we initialize FCV only after rebuilding the index which is over here. As a result, we break the assumption mentioned here. Also, if we upgrade/restart the node with mongodb binary version 4.3+, we would crash the server as part of startup index sanity check (Sanity check got introduced only from mongodb 4.3+). |
| Comments |
| Comment by Githook User [ 27/Feb/20 ] |
|
Author: {'name': 'Louis Williams', 'username': 'louiswilliams', 'email': 'louis.williams@mongodb.com'}Message: |
| Comment by Githook User [ 27/Jan/20 ] |
|
Author: {'username': 'louiswilliams', 'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com'}Message: |
| Comment by Githook User [ 24/Jan/20 ] |
|
Author: {'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams', 'name': 'Louis Williams'}Message: When we rebuild unfinished unique indexes during startup recovery, the |