[SERVER-6825] Hard shutdown can leave replication in unrestartable state Created: 22/Aug/12 Updated: 11/Jul/16 Resolved: 22/Aug/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0-rc2, 2.3.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Leading to the member fatal asserting on restart. |
| Comments |
| Comment by auto [ 22/Aug/12 ] |
|
Author: {u'date': u'2012-08-22T10:39:55-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: During initial sync, you must apply updates as updates and upserts as upserts, However, during normal replication, we need all updates to be upserts. |
| Comment by auto [ 22/Aug/12 ] |
|
Author: {u'date': u'2012-08-22T10:39:55-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: During initial sync, you must apply updates as updates and upserts as upserts, However, during normal replication, we need all updates to be upserts. |
| Comment by Eric Milkie [ 22/Aug/12 ] |
|
If, in addition to minValid, we also had something like a maxValid value that showed how far we attempted to write operations (this would be updated when we begin a batch), we might then ignore update errors while replaying ops less than "maxValid"? |