[SERVER-26065] racy test in autodiscover_config_rs_from_secondary.js Created: 12/Sep/16  Updated: 25/Jan/17  Resolved: 11/Nov/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.3.12
Fix Version/s: 3.4.0-rc4

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-27035 rs.compareOpTimes() throws exception ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2016-10-10, Sharding 2016-10-31, Sharding 2016-11-21
Participants:
Linked BF Score: 0

 Description   

Test kills all nodes in a config repl set except for one and tries to perform a read on it. However, it is possible that a background thread in mongos advances the latest config server opTime that the surviving secondary has yet to replicate and this will cause the read after opTime to timeout.



 Comments   
Comment by Githook User [ 11/Nov/16 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-26065 Wait for remaining secondaries in autodiscover_config_rs_from_secondary.js to have the same opTime before doing a query with readAfterOptime
Branch: master
https://github.com/mongodb/mongo/commit/e37cdd0c492aac1533e185636828ed8a714847a7

Comment by Githook User [ 09/Nov/16 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-26065 Write more generic optime comparator function
Branch: master
https://github.com/mongodb/mongo/commit/a38156adf985f57861f7f00e1dfa24183abcc105

Generated at Thu Feb 08 04:11:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.