[SERVER-28046] Increase timeouts in replsets/read_committed_on_secondary.js to 10 minutes Created: 17/Feb/17 Updated: 06/Dec/17 Resolved: 07/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.7, 3.5.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.4
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The failure in https://jira.mongodb.org/browse/BF-4726 occurred when executing a readConcern=majority read on a document that was written with writeConcern=majority. Thus, it appears that the failure was likely caused by a mongod taking a long amount of time to read a document from local storage (not making any network requests to other nodes). The functions `doDirtyRead` and `doCommittedRead` should have the `maxTimeMS` values in their find commands increased to 10 minutes, so as to account for any potentially slow test machines. |
| Comments |
| Comment by Githook User [ 14/Jul/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit a0f582f5238b3382195cbc22d3803d6955760839) |
| Comment by Githook User [ 17/Apr/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |