Avoid fasserting in a tenant migration if recipient primary calls startup on oplog buffer after it steps down

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Repl 2021-02-22
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In a tenant migration, if we step down the recipient primary before it has started up the oplog buffer, it seems it will fassert and fail here. We should probably handle this case by returning an error status instead of fasserting.

            Assignee:
            Vishnu Kaushik
            Reporter:
            Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: