[SERVER-61593] Test command waitForMemberState should be interruptible Created: 18/Nov/21 Updated: 29/Oct/23 Resolved: 19/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| 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: | Replication 2021-11-29 |
| Participants: |
| Description |
|
We currently use the replication coordinator method waitForReplState only in the test command waitForReplState. It appears the library calling this uses assert_soon, thus it tolerates interrupts, but in fact this method is not interruptible. Since it's called with an opCtx active, that means it can block anything which requires opCtxs to be killed; currently the only example is storage change on initial sync. We should make it take an Interruptible or OperationContext. |
| Comments |
| Comment by Githook User [ 19/Nov/21 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |