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

Enforce w:1 for creation of transactions table on step-up

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.0-rc4, 4.3.1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Repl 2019-07-01, Repl 2019-07-15
    • 9

      We create the transactions table on step-up via a DBDirectClient call. That will inherit the default writeConcern, which is a problem if the user changed it from w:1. In that case, the call will wait on that WC immediately, while also holding locks (particularly the RSTL in mode X, from the step-up hook). We do not want to do this, as that can block other processes, including servicing find commands for replication.
      We should instead create the transactions table via the storage interface, as that will give us w:1 in all cases.

            Assignee:
            jason.chan@mongodb.com Jason Chan
            Reporter:
            vesselina.ratcheva@mongodb.com Vesselina Ratcheva (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: