[SERVER-40164] yieldLocksForPreparedTransactions while calling killSessionsAction should set the kill reason as ErrorCodes::InterruptedDueToStepDown if it is called during step down. Created: 15/Mar/19 Updated: 29/Oct/23 Resolved: 28/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.13 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2019-04-22, Repl 2019-06-03 |
| Participants: |
| Description |
|
Currently yieldLocksForPreparedTransactions while calling killSessionsAction, it doesn't pass the reason for killing the operation. As a result, if we call yieldLocksForPreparedTransactions during step down, the operation (that checked out the session) will be mark killed with default reason "ErrorCodes::Interrupted". |
| Comments |
| Comment by Githook User [ 28/May/19 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |