[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: | |||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
|
| 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 |
| 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? |