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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.0-rc4, 4.3.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      Repl 2019-07-01, Repl 2019-07-15
    • Linked BF Score:
      9

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jason.chan Jason Chan
              Reporter:
              vesselina.ratcheva Vesselina Ratcheva
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: