[SERVER-31927] RollbackTest fixture might erroneously return from awaitReplication call in transitionToRollbackOperations Created: 11/Nov/17 Updated: 02/Mar/18 Resolved: 11/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Eddie Louie |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||
| Sprint: | TIG 2018-1-15, TIG 2018-1-1, TIG 2017-12-18, TIG 2018-1-29 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 51 | ||||||||||||||||
| Description |
|
Currently, the rollback_test.js test fixture will await replication when calling transitionToRollbackOperations. If a node is in the middle of ROLLBACK, though, when this gets called, the awaitReplication call will ignore the node that is currently rolling back and return having checked 0 secondaries. It needs to properly wait for the ROLLBACK to occur, and for the node to fully transition to SECONDARY. |
| Comments |
| Comment by Robert Guo (Inactive) [ 11/Jan/18 ] |
|
The issue described in this ticket has been fixed by a refactor of the transition table in |