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

Ghostsyncing does not retry after a network failure

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 2.4.3, 2.5.0
    • 2.4.5, 2.5.1
    • Replication
    • None
    • ALL

    Description

      It needs to try to reconnect immediately.
      Non-ghostsync updates do not have this problem because the updater runs in a loop and keeps trying until it succeeds in transmitting the oplog position update.
      The current Ghostsync code gives up if there is a network failure and doesn't get resolved until the next write is applied. This is 'ok' if there are lots of writes, but pretty bad if there are no writes for a while (because write concern on the primary will not see it).

      This logic will be better solved by SERVER-6071.

      Attachments

        Activity

          People

            milkie@mongodb.com Eric Milkie
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: