[SERVER-18326] Rollback attempted during initial sync is fatal Created: 05/May/15 Updated: 19/Sep/15 Resolved: 06/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.3, 3.1.2 |
| Fix Version/s: | 3.0.4, 3.1.3 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | UT | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
When initial sync resets state and clears the oplog it is possible for the rollback logic to attempt and fail a rollback leading to a controlled shutdown. The rollback logic should ignore an empty oplog during rollback to accommodate for initial/re-sync running at the same time. |
| Comments |
| Comment by Githook User [ 08/Jun/15 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: (cherry picked from commit e74dc41583dde9e40e08f97c6bb6a307a973a199) |
| Comment by Githook User [ 06/May/15 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |