[SERVER-48564] Fix the log race in initial_sync_fcv_downgrade.js Created: 03/Jun/20 Updated: 29/Oct/23 Resolved: 04/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| 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: | Repl 2020-06-15 | ||||
| Participants: | |||||
| Linked BF Score: | 25 | ||||
| Description |
|
This check can be racy as it might read the logs generated by scenario 2. Instead use waitForNewlyAddedRemovalForNodeToBeCommitted to avoid the log race. |
| Comments |
| Comment by Suganthi Mani [ 04/Jun/20 ] |
|
Not sure why git hook wasn't working. Anyways, this issue is fixed by this commit https://github.com/mongodb/mongo/commit/7e41813dfa46b5357ca85a35afdd8ba86549cedd
|