Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13389

Investigate changes in SERVER-45468: Create a DBClientCursor in the new oplog fetcher

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.4
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      3
    • Sprint:
      ServerDocs2020: Jun22-Jun26, ServerDocs2020: Jun29 - Jul2

      Description

      Description

      Downstream Change Summary

      Added a new server parameter called oplogFetcherUsesExhaust which can be set at startup. It will set whether oplog fetching will use exhaust cursors or not.

      This ticket should also cover what this means; i.e. streaming replication vs oplog batches.

      Description of Linked Ticket

      As a part of this ticket, we should investigate whether we can set the socket timeout on the connection before the cursor is initialized (and the find command is run) and after the cursor is initialized. If possible, this would allow us to set a timeout for when the find is running and a separate getMore timeout.

      We should also implement logic to create a new cursor when an error is encountered.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kanchana.sekhar Kanchana Sekhar
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Githook User Githook User
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 19 weeks, 2 days ago
                Date of 1st Reply: