[SERVER-50464] quiesce_mode.js does not properly wait for the proper find command to be established before entering quiesce mode Created: 21/Aug/20 Updated: 29/Oct/23 Resolved: 24/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 4.5 Required |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Jason Chan |
| 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-08-24, Repl 2020-09-07 | ||||
| Participants: | |||||
| Linked BF Score: | 14 | ||||
| Description |
|
Although we call findCmdFailPoint.wait(), this doesn't really help because wait() will only wait for the failpoint block to be entered once more from any command. The way the failpoint is defined, we will increment the timesEntered field for the failpoint on every find command while the failpoint is enabled. However, we will only hang the operation if the read is applied on the namespace that we pass in. Therefore, calling wait() will not guarantee that we have actually created the hanging operation that we care about on the primary. |
| Comments |
| Comment by Githook User [ 24/Aug/20 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |