[SERVER-46306] Make cancelCommand integration tests wait for the command to acquire a connection Created: 21/Feb/20 Updated: 29/Oct/23 Resolved: 22/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| 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: | Service Arch 2020-02-24 |
| Participants: |
| Description |
|
The current implementation of CancelRemotely and CancelRemotelyTimedOut expects the command being cancelled to have already acquired a connection by the time cancelCommand starts. This is not always true, and when cancelCommand is run before the command has acquired a connection, cancelCommand immediately fulfills the promise with CallbackCancelled, which causes the checks in the these tests to fail. These tests should wait for the command to acquire a connection before calling cancelCommand (e.g. using a failpoint). |
| Comments |
| Comment by Githook User [ 21/Feb/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'username': 'cheahuychou', 'email': 'cheahuychou.mao@mongodb.com'}Message: |