[SERVER-20655] During recovery replicas should truncate the oplog to start position of the failed batch Created: 26/Sep/15 Updated: 15/Oct/15 Resolved: 12/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | 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 | ||||||||||||||||
| Sprint: | RPL A (10/09/15), Repl B (10/30/15) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
We need to truncate the oplog to the start of the active/failed oplog batch when we recover from a failed batch. While database operations are idempotent, the inserting of the oplog entries are not, and need to be removed (via truncate) before we apply again, much like rollback does. |
| Comments |
| Comment by Githook User [ 12/Oct/15 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |
| Comment by Githook User [ 02/Oct/15 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: Revert " This reverts commit 3617494d8c54e98767ec48537589a3b05bbc2667. |
| Comment by Githook User [ 01/Oct/15 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |