[SERVER-40046] txn_being_applied_to_secondary_cannot_be_killed.js must disable sharding Created: 08/Mar/19 Updated: 29/Oct/23 Resolved: 08/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2019-04-22 | ||||
| Participants: | |||||
| Linked BF Score: | 14 | ||||
| Description |
|
This test depends on one of the secondaries in shard 0 advancing while another is held at a failpoint. If it happens that the secondary which is supposed to advance has the other secondary as its sync source, that can't happen. So chaining should be disabled to ensure both secondaries sync from the primary directly. |
| Comments |
| Comment by Githook User [ 11/Apr/19 ] |
|
Author: {'email': 'matthew.saltz@mongodb.com', 'name': 'Matthew Saltz', 'username': 'saltzm'}Message: |
| Comment by Matthew Russotto [ 08/Mar/19 ] |
|
Program Management Note
|