[SERVER-41433] Increase writeConcern wtimeout of commitTransaction in txn_commit_optimizations_for_read_only_shards.js Created: 31/May/19 Updated: 29/Oct/23 Resolved: 17/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Lamont Nelson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | esha-summer-2019-neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Sprint: | Sharding 2019-06-17, Sharding 2019-07-01 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 19 | ||||||||
| Description |
|
The current wtimeout of 3000ms seems slightly too low, as there was one failure in the continuous integration system due to the write taking slightly more than 3000ms to replicate. I think doubling it to 6000ms should be enough, since the failure only occurred once in the span of 2 months, and increasing it too much will cause the test to take a long time. |
| Comments |
| Comment by Githook User [ 19/Jun/19 ] |
|
Author: {'name': 'Lamont Nelson', 'email': 'lamont.nelson@mongodb.com'}Message: (cherry picked from commit bf7c0a688e10fe2c545727df19c0621593d993f8) |
| Comment by Lamont Nelson [ 17/Jun/19 ] |
|
The write timeout for this test was increased to 6s. |
| Comment by Githook User [ 17/Jun/19 ] |
|
Author: {'name': 'Lamont Nelson', 'email': 'lamont.nelson@mongodb.com'}Message: |