Use lastCommittedOpTime in InvocationArgs as the clientsLastKnownCommittedOpTime in the next synthetic getMore request

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      • Set the lastKnownCommittedOpTime field in appendReplyMetadata if the command is a getMore on oplog with tailable exhaust cursor.
      • Use the lastKnownCommittedOpTime in ReplyBuilderInterface::nextInvocation (from the last response) as the clientsLastKnownCommittedOpTime for the next getMore command as if that’s from the client.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: