[SERVER-15209] Fix updating optimes from remote nodes Created: 10/Sep/14 Updated: 10/Dec/14 Resolved: 17/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Currently, it is possible for a node to erroneously update its own lastAppliedOptime when all of these conditions are true:
In such a situation, we rewind our own optime in the slavemap, but do not update the legacy replset's lastappliedoptime, which causes an fassert failure. |
| Comments |
| Comment by Eric Milkie [ 17/Oct/14 ] |
|
This is a problem only in legacy repl, at this point. |
| Comment by Githook User [ 10/Sep/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |