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

Internal task _reconfigToRemoveNewlyAddedField() should be resilient to stepdown errors.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Replication
    • ALL
    • 142

    Description

      Due to SERVER-70127, system operations are now killable on stepdown by default. This change means that internal operations like _reconfigToRemoveNewlyAddedField() can be interrupted by stepdown (see this code which can throw interruption errors) , potentially resulting in the throwing of InterruptedDueToReplStateChange error code. Unfortunately, _reconfigToRemoveNewlyAddedField don't catch these errors. Additionally, since this internal task runs on the internal thread without error handling, it can cause a server crash.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: