[SERVER-12490] jsTest.authenticate causing ReplSetTest.getMaster to time out Created: 27/Jan/14 Updated: 10/Dec/14 Resolved: 29/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
In auth enabled tests, every call to getDB() will trigger a call to jsTest.authenticate(), which has it's own built-in assert.soon until it succeeds. In some of the replica set shard setup, this appears to never succeeded, and thus making getDB() call take way more time that it should. This has a chain reaction of making the assert.soon inside ReplSetTest.getMaster timeout. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 29/Jan/14 ] |
|
This is really just a duplicate of |
| Comment by Randolph Tan [ 27/Jan/14 ] |
|
Attaching sample test failure log - addshard4.log. |