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

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

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2020-10-19, Repl 2020-11-02
    • 46

      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)

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

              Created:
              Updated:
              Resolved: