[SERVER-20761] stepdown_long_wait_time.js fails intermittently with "waiting for state indicator" Created: 02/Oct/15 Updated: 25/Jan/17 Resolved: 06/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.1.8 |
| Fix Version/s: | 3.1.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | RPL A (10/09/15) |
| Participants: |
| Description |
|
The test should be waiting for the primary to step down separately from waiting for the secondary to start a new election to succeed the primary. Two failures of stepdown_long_wait_time.js observed in replicasets_auth suite on Enterprise Windows today. The test failure mode is that an election is expected to succeed in 30 seconds; the election does not succeed. Failed tasks:
Excerpt from first failure above:
|
| Comments |
| Comment by Githook User [ 06/Oct/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Benety Goh [ 05/Oct/15 ] |
|
466f05960f OS X 10.8 replicasets_WT https://logkeeper.mongodb.org/build/560e90d390413021b1b394b2/test/560ea47cbe07c4135fb52303 |