Fix bugs related to FCBIS initial node becoming primary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Replication 2021-11-15
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      File copy based initial sync drops the local.replset.election (last vote) collection. While this is correct for backup because the node is subsequently restarted, for FCBIS we need to write a default last vote instead (for backup, that document is written when the node is restarted as a replica set)

      The JournalListener is reset when we restart storage. We need to restore it on the new storage engine or Replication will never advance its majority point as primary.

            Assignee:
            Matthew Russotto (Inactive)
            Reporter:
            Matthew Russotto (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: