[SERVER-47759] Resolve race condition in oplog fetcher unittests Created: 24/Apr/20 Updated: 29/Oct/23 Resolved: 05/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 4.5 Required |
| Fix Version/s: | 4.4.0-rc7, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Xuerui Fa |
| 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 | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Sprint: | Repl 2020-05-04, Repl 2020-05-18 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
It seems like the linked BF happens because of a race condition. We shut down the mocked remote server and then start up the oplog fetcher. After we start up the oplog fetcher, we assert that it is active. This seems to be the line that is flaky, since it seems possible for the node to try to connect, and fail, before the assertion. |
| Comments |
| Comment by Githook User [ 20/May/20 ] |
|
Author: {'name': 'Xuerui Fa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: (cherry picked from commit 0f45c01312438ff8bd424033512a85af1b59b3bd) |
| Comment by Githook User [ 05/May/20 ] |
|
Author: {'name': 'Xuerui Fa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: |