[SERVER-8222] connections_opened.js failing when run under small_oplog Created: 17/Jan/13  Updated: 11/Jul/16  Resolved: 18/Jan/13

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.3.2
Fix Version/s: 2.4.0-rc0

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

buildscripts/smoke.py --nojournal --small-oplog jstests/connections_opened.js

https://bamboo.10gen.com/browse/MONGODB-COMMITLINUX-SMALLOPLOG-211/log

From what I can tell, it seems like the problem is that when the test starts it starts a resync, at some point that resync finishes and closes the connection it was using, causing the connection numbers to be off by one in the test.

The solution may be just to skip this test when running with small oplog (there's already a section of smoke.py for skipping tests when running with small oplog), but I don't know enough about how master/slave works and why this resync is happening to tell if there's a better way (perhaps by preventing the resync, waiting for it to terminate before starting the test, or somehow preventing it from messing with the connection numbers).



 Comments   
Comment by Eric Milkie [ 18/Jan/13 ]

Yes, the small oplog test will generate other connections that will cause the counts to be off. I took your test out of small-oplog test phase.

Comment by auto [ 18/Jan/13 ]

Author:

{u'date': u'2013-01-18T21:28:28Z', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}

Message: SERVER-8222 remove connections_opened.js from small-oplog test
Branch: master
https://github.com/mongodb/mongo/commit/1a4363cb481ab62f5199eb6f2adf2ffbc04b542d

Generated at Thu Feb 08 03:16:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.