[SERVER-50546] indexbg_restart_secondary.js fails when majority read concern is off and resumable index builds is on Created: 26/Aug/20 Updated: 29/Oct/23 Resolved: 26/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Execution Team 2020-09-07 |
| Participants: |
| Description |
|
This test is relying on a static check that does not take into account support for committed reads. As a result, the test looks for a resumable index build message that is never logged. |
| Comments |
| Comment by Githook User [ 26/Aug/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |