Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-44708

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

XMLWordPrintableJSON

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

      • 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:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: