[DOCS-14257] Investigate changes in SERVER-54608: dropIndexes needs to make the same assertions on primary and secondary nodes Created: 26/Feb/21 Updated: 13/Nov/23 Resolved: 19/Aug/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.4.5, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Ian Fogelman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 2 years, 25 weeks ago | ||||||||
| Epic Link: | DOCSP-15042 | ||||||||
| Description |
DescriptionDownstream Change Summary The dropIndexes command cannot drop any ready indexes while there are any in-progress index builds. Description of Linked TicketThe applyOps path for dropIndexes makes an assertion that the primary does not. This can lead to a bug that generates an invalid oplog sequence and causes all secondaries to stop replicating. There is a bug that can be described by the following sequence in its simplest form:
We need to either a) assert on the primary that no index builds are in progress when a single index is dropped, or b) remove the assertion for the applyOps path. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 18/Aug/21 ] |
|
Author: {'name': 'ian fogelman', 'email': 'ian.fogelman@mongodb.com', 'username': 'ianf-mongodb'}Message: |