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

OplogBufferCollection methods should not fassert on "InterruptedDueToReplStateChange" error, and instead allow the callers to handle them.

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0, 7.3.0-rc4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v7.3
    • Execution Team 2023-12-11, Execution Team 2024-02-05, Execution Team 2024-02-19, Execution Team 2024-03-04
    • 8

      Since we interrupt all opCtx created on behalf of POS services when the node steps down, OplogBufferCollection methods (used internally by POS services, such as tenant migration and merge) can trigger fasserts, as seen in the BF. Instead of fasserting, throw an exception and let the caller handle those errors.

      As part of this ticket, audit other fassert places in oplog_buffer_collection.cpp file to see if they need a similar treatment.

            suganthi.mani@mongodb.com Suganthi Mani
            suganthi.mani@mongodb.com Suganthi Mani
            0 Vote for this issue
            3 Start watching this issue