[SERVER-45934] Race in ExhaustCursorUpdatesLastKnownCommittedOpTime integration test Created: 03/Feb/20 Updated: 29/Oct/23 Resolved: 04/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| 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-02-10 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 5 | ||||||||||||
| Description |
|
There is a race between how the curOpMatch was generated and the queryCursor receiving a new batch from getMore. When the cursor receives a new batch, it sets the cursorId to 0 before parsing the response. So it is possible for the test thread to race with the queryThread and get a wrong cursorId 0. Therefore, it is possible for a test to use a wrong curOpMatch {command.getMore: 0} in confirmCurrentOpContents, resulting in test failures. |
| Comments |
| Comment by Githook User [ 04/Feb/20 ] |
|
Author: {'username': 'ldennis', 'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com'}Message: |