[SERVER-43353] index_stepdown_init.js must handle error messages other than IndexBuildAborted Created: 16/Sep/19 Updated: 29/Oct/23 Resolved: 01/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | 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 2019-10-07 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 17 | ||||||||
| Description |
|
index_stepdown_init.js depends on finding "IndexBuildAborted: Index build aborted: " in the server's error message logging. However, the particular error message that the stepdown interruption produces is not limited to the IndexBuildsCoordinator/MultiIndexBlock code. For example, the error message can be produced by the repl code layer. One solution is to just require "Index build failed", which we prepend to all index build failures at the higher level. Otherwise, all possible replication error messages must be handled in the JS test. For example, the test failure prompting this ticket had a NotMaster error; and there may be other possible error messages See the linked test failure for specifics. |
| Comments |
| Comment by Githook User [ 01/Oct/19 ] |
|
Author: {'username': 'louiswilliams', 'email': 'louis.williams@mongodb.com', 'name': 'Louis Williams'}Message: |