[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:
Related
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:

  • the node is PRIMARY
  • the node was SECONDARY in the past and has chained through another secondary
  • the node does further writes before receiving a handshake from the chaining secondary

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: SERVER-15209 remove fassert temporarily
Branch: master
https://github.com/mongodb/mongo/commit/e1c24123e023b47d8b279f77ba00cbf61e5a1347

Generated at Thu Feb 08 03:37:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.