[SERVER-41315] fix read_operations_during_rollback.js Created: 24/May/19 Updated: 29/Oct/23 Resolved: 24/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.12 |
| 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 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
This does not necessarily throw if the error message is returned fast enough before the connection is killed. On transition to rollback, we mark operations killed first then close the connections which calls _performPostMemberStateUpdateAction. So if the error message gets back to the client during that window, client doesn't necessarily throw but instead gets InterruptedDueToReplStateChange. This is new behavior introduced in this commit ( So we need to change the test not to assert.throw. |
| Comments |
| Comment by Githook User [ 24/May/19 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |