[SERVER-66758] Remove usage of CancelableOperationContext when cleaning up internal sessions in setFCV Created: 25/May/22 Updated: 29/Oct/23 Resolved: 31/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc9, 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jason Zhang | Assignee: | Jason Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v6.0, v5.0
|
||||||||
| Sprint: | Sharding NYC 2022-05-30 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 128 | ||||||||
| Description |
|
Currently the usage of CancelableOperationContexts lead to unspecific errors being thrown when these opCtxes are interrupted. There is a narrow window in setFCV we use a CancelableOperationContext to do internal session cleanup where interruptions would result in a nonretryable error being thrown. This causes internal_sessions_setfcv_wait_for_transaction_coordinator_cleanup.js to be a bit flaky since it relies on the retryablility of the setFCV on stepdown. |
| Comments |
| Comment by Blake Oler [ 09/Jun/22 ] |
|
Requesting backport to 5.0 to resolve BF-25478. |
| Comment by Githook User [ 06/Jun/22 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}Message: |
| Comment by Githook User [ 27/May/22 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}Message: |