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

recoverFromOplogAsStandalone does not relax index constraints

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.20, 4.2.9
    • Component/s: Indexing, Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2
    • Sprint:
      Repl 2020-07-27, Repl 2020-08-10

      Description

      Normal replication recovery does, because shouldRelaxIndexConstraints returns "true" during STARTUP but shouldRelaxIndexConstraints returns "false" on a standalone, so recoverFromOplogAsStandalone does not.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-49529 setTableLogging error at startup while creating index entry, in backup/restore test

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-49530 fix final index build phase for oplog recovery as a standalone mode

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-49924 Forward-port SERVER-49527 to master branch

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              judah.schvimer Judah Schvimer
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: