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

Don't try to cleanly shut down initial syncer when config changes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.2
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2020-10-19, Repl 2020-11-02
    • Linked BF Score:
      46

      Description

      In 4.4 (but no other version), we kill the syncing node with a LOG_FATAL when an initial sync is happening and it is removed from the configuration. We attempt to cleanly shut down the initial syncer first. However, if this results in the initial syncer running out of attempts, we will instead get a LOG_FATAL with that error instead.

      We should just LOG_FATAL with the error about being removed; there's no point in trying to cleanly shut down when we're going to kill the server anyway.

      (This was uncovered when cancellation of the initial syncer was fixed by SERVER-50320)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matthew.russotto Matthew Russotto
              Reporter:
              matthew.russotto Matthew Russotto
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: