_flushForQueryPredicate should handle malformed oplog entries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • v4.0, v3.6
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During oplog application, SessionUpdateTracker::_flushForQueryPredicate expects an oplog entry for "config.transactions" to contain an "_id" field which is an object. If it is not, we assert with code 10065 (in BSONElement::Obj()). Since we do not prevent arbitrary updates to config.transactions, we must be able to survive malformed entries.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Matthew Russotto (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: