[SERVER-48596] IndexBuildsCoordinator::abortCollectionIndexBuilds() should return early if there are no active index builds Created: 04/Jun/20 Updated: 29/Oct/23 Resolved: 16/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Benety Goh | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2020-06-29 | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Description |
|
This function is called during collection drops to stop active index builds. However, it logs a message with the ID 23879 and the text "About to abort all index builders" message even when there are no active index builds. We should consider skipping this log message depending on collIndexBuilds.size() |
| Comments |
| Comment by Githook User [ 16/Jun/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |