[SERVER-5790] sharding_rs2.js failing during slowNightly tests Created: 08/May/12  Updated: 11/Jul/16  Resolved: 25/May/12

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: 2.1.2

Type: Improvement Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Nightly Linux 64-bit


Participants:

 Description   

 m31100| Tue May  8 08:51:47 [rsHealthPoll] replSet member ip-10-110-9-236:31103 is now in state SECONDARY
assert: [100] != [3] are not equal : B4
Error("Printing Stack Trace")@:0
()@src/mongo/shell/utils.js:37
("[100] != [3] are not equal : B4")@src/mongo/shell/utils.js:58
(100,3,"B4")@src/mongo/shell/utils.js:88
@/mnt/home/buildbot/slave/Linux_64bit_Nightly/mongo/jstests/slowNightly/sharding_rs2.js:113
 
Tue May  8 08:51:47 uncaught exception: [100] != [3] are not equal : B4
failed to load: /mnt/home/buildbot/slave/Linux_64bit_Nightly/mongo/jstests/slowNightly/sharding_rs2.js

http://buildbot.mongodb.org/builders/Nightly%20Linux%2064-bit/builds/967/steps/test_1/logs/stdio



 Comments   
Comment by auto [ 25/May/12 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-5790 check that ops are lte not ==, since other ops can occur in parallel.
Branch: master
https://github.com/mongodb/mongo/commit/81c3b82384ea75be18c8da4a9c97dc52bd6a2c08

Comment by Eric Milkie [ 25/May/12 ]

The nightly Linux 64-bit build is failing repeatedly on this test (which means it runs no other tests at all, from any suite):
http://buildbot.mongodb.org/builders/Nightly%20Linux%2064-bit%20concurrency/builds/55

Comment by Greg Studer [ 22/May/12 ]

Pretty sure it's not related to the push - the test is a bit fragile b/c it measures the number of queries to secondaries in a time period, which can happen from many other sources. This time I think it happened b/c another secondary happened to pull a status update from this node.

Changing type of ticket to improvement, will see if there's a better way to measure this without using direct operation counts.

Comment by Ian Whalen (Inactive) [ 21/May/12 ]

After your changes we're now getting errors in test B3:

http://buildbot.mongodb.org/builders/Nightly%20Linux%2064-bit/builds/978/steps/test_1/logs/stdio

Comment by Greg Studer [ 10/May/12 ]

Think this is now fixed, will close once confirmed.

Comment by auto [ 10/May/12 ]

Author:

{u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: SERVER-5790 buildbot sharding_rs2.js wait for secondary status and replication before checking slaveOk'd count
Branch: master
https://github.com/mongodb/mongo/commit/9c1fde019c6d1f6023e7576de58865bab06741a2

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