Info
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.
Top User Comments
xgen-internal-githook commented on Fri, 14 Jul 2017 20:51:14 +0000:
Author:
{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}
Message: SERVER-28046 increase maxTimeMS in read_committed_on_secondary.js
(cherry picked from commit a0f582f5238b3382195cbc22d3803d6955760839)
Branch: v3.4
https://github.com/mongodb/mongo/commit/c161a23f10dbe960d4b9c49b58bd22fe415bf1b9
xgen-internal-githook commented on Mon, 17 Apr 2017 17:56:20 +0000:
Author:
{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}
Message: SERVER-28046 increase maxTimeMS in read_committed_on_secondary.js
Branch: master
https://github.com/mongodb/mongo/commit/a0f582f5238b3382195cbc22d3803d6955760839
