[SERVER-48293] remove inactive index builds from config.system.indexBuilds Created: 19/May/20 Updated: 29/Oct/23 Resolved: 16/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.0, 4.4.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Vishnu Kaushik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | newgrad | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||||||||||
| Sprint: | Execution Team 2020-09-21 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 30 | ||||||||||||||||||||||||
| Description |
|
After an index build is completed (committed/aborted) the document representing the active index build state in config.system.indexBuilds is removed by the IndexBuildsCoordinator. This was done in |
| Comments |
| Comment by Githook User [ 09/Nov/21 ] |
|
Author: {'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: (cherry picked from commit cc248c4286d45eee06e2d66cdd52cd7cbae5b593) |
| Comment by Githook User [ 16/Sep/20 ] |
|
Author: {'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |
| Comment by Benety Goh [ 21/May/20 ] |
|
Having additional checks in the voteCommitIndexBuild command would definitely help in addressing the underlying problem. |
| Comment by Dianna Hohensee (Inactive) [ 20/May/20 ] |
|
Could we have the secondary vote not write to the collection if the index build on the primary is already done? Maybe a mutex – after taking the IX locks --for updating the collection documents? Might be easier than creating an asynchronous task. |