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

recover_prepared_transactions_startup_secondary_application.js should wait for node to be in the secondary state before reading from it

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.2.0-rc3, 4.3.1
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Repl 2019-06-17, Repl 2019-07-01
    • 20

    Description

      recover_prepared_transactions_startup_secondary_application.js waits for all writes before the nodes went into recovery to be majority committed, but it doesn't wait for the node to transition back into the secondary state. This can cause a test to fail if the node has reconstructed these prepared transactions (and thus cause the majority commit point to advance), but hasn't exited recovering mode.

      Attachments

        Activity

          People

            samy.lanka@mongodb.com Samyukta Lanka
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: