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

Improve observability of imminent initial sync failure on the source node

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Replication

    Description

      Initial sync can time out when the syncing node is repeatedly unable to open a cursor for an oplog fetcher on the source node.

      When we timeout because the syncing node is unable to create a cursor for the oplog fetcher, the source node is responsible for preventing this cursor from being created. We want to know when initial sync is at risk of failing on the source node so we can collect stack traces. Currently, it is difficult to diagnose why we're unable to create this cursor on the source node.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            edwin.zhou@mongodb.com Edwin Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: