[SERVER-31213] Retry retryable writes at least once in retryable_writes_jscore_passthrough Created: 21/Sep/17 Updated: 30/Oct/23 Resolved: 11/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding36-passthrough-testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-10-02, Sharding 2017-10-23 |
| Participants: |
| Description |
|
Currently the retryable_writes_jscore_passthrough attaches txnNumbers to all retryable write commands, but will only retry them on a network error. To increase coverage of the retryable writes project, an override should be created and loaded that will force all retryable writes to be retried at least once even on success. |
| Comments |
| Comment by Githook User [ 11/Oct/17 ] |
|
Author: {'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}Message: |
| Comment by Gregory McKeon (Inactive) [ 26/Sep/17 ] |
|
kaloian.manassiev will we block the rc for this, or is this rc0 becaue we expect it to complete soon? |