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

    XMLWordPrintable

    Details

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

      Description

      • 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.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-repl Backlog - Replication Team
            Reporter:
            lingzhi.deng Lingzhi Deng
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: