[SERVER-41755] Fail loudly in tests if transaction coordinator receives non-retryable error for commitTransaction Created: 14/Jun/19 Updated: 27/Oct/23 Resolved: 29/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Sharding 2019-07-01, Sharding 2019-07-15, Sharding 2019-07-29, Sharding 2019-08-12, Sharding 2019-08-26, Sharding 2019-09-09 | ||||
| Participants: | |||||
| Linked BF Score: | 21 | ||||
| Description |
|
If it receives InvalidOptions for example, it should fassert and fail loudly in our tests (though it can't in production because inputs over the wire cannot cause fasserts). |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 29/Aug/19 ] |
|
Closing as Works as Designed based on offline agreement with Judah. |
| Comment by Esha Maharishi (Inactive) [ 14/Jun/19 ] |
|
Today, the coordinator will keep retrying on that error, which is maybe loud enough for our tests? |