[SERVER-38057] transactions_error_labels.js should unset the failCommand failpoint before shutting down Created: 09/Nov/18 Updated: 29/Oct/23 Resolved: 12/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| 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 2018-11-19 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
This test sets a fail point to fail all inserts on a shard to test error labels, but it never unsets it, so if the sessions collection is refreshed on the shard after the fail point has been set, the refresh will never complete and the test will hang in the check uuids consistency hook that runs after each test when it waits for each shard to finish any ongoing metadata refreshes. |
| Comments |
| Comment by Githook User [ 12/Nov/18 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |