[SERVER-7359] timeout in repl_monitor_stress.js waiting for node to become master Created: 15/Oct/12 Updated: 21/Mar/13 Resolved: 21/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
| Comments |
| Comment by Ian Whalen (Inactive) [ 21/Mar/13 ] | |||||||
|
this is probably unrelated - the correct ticket related to the current failure is | |||||||
| Comment by Ian Whalen (Inactive) [ 21/Mar/13 ] | |||||||
|
I'm now seeing identical error messages consistently on the Windows 64 build on the 2.2 branch:
| |||||||
| Comment by Randolph Tan [ 17/Oct/12 ] | |||||||
|
Based from the logs, the node that was intended to become primary during the test setup did not become the priority despite having the highest priority. This synchronization step would become unnecessary when ported to the cpp unit test using the mock clients. |