[SERVER-5698] "assert failed : reconfig worked" in fastsync.js Created: 24/Apr/12  Updated: 11/Jul/16  Resolved: 29/May/12

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

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

http://buildbot.mongodb.org/builders/Nightly%20Linux%2064-bit%20Legacy/builds/900/steps/test_9/logs/stdio


Issue Links:
Duplicate
is duplicated by SERVER-5943 assert failed : reconfig worked in fa... Closed
Operating System: ALL
Participants:

 Description   

http://buildbot.mongodb.org/builders/Nightly%20Linux%2064-bit%20Legacy/builds/900/steps/test_9/logs/stdio



 Comments   
Comment by auto [ 29/May/12 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: Fix fastsync test SERVER-5698
Branch: master
https://github.com/mongodb/mongo/commit/1c002b2f63eb209e0fcaba7b65c7a42fce0c18c1

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

most recently seen here: http://buildbot.mongodb.org/builders/Linux%2032-bit%20debug/builds/1775/steps/test_7/logs/stdio

Comment by Kristina Chodorow (Inactive) [ 24/Apr/12 ]

Yeah, it needs to make sure it can connect to 31001. I thought sargs.start() would wait for that, but I guess not...

Comment by Eric Milkie [ 24/Apr/12 ]

Right, so does the test need to synchronize with the new server startup before it attempts to do a reconfig?

Comment by Kristina Chodorow (Inactive) [ 24/Apr/12 ]

Not sure what you mean, it looks like the reconfig tried to reach 31001 before it was listening on that port.

Comment by Eric Milkie [ 24/Apr/12 ]

does fastsync need a sync point after starting the mongodrunner but before running reconfig?

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