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

clear the "needing size adjustment" set at the beginning of replication rollback

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0-rc6, 4.1.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Repl 2018-06-04, Repl 2018-06-18
    • Linked BF Score:
      65

      Description

      One problem we've noted is that this call to mark collections as needing size adjustment is not gated on being in storage recovery, which is what it's meant for. This means any collections that are created are marked as needing size adjustment, even if later writes would ensure they have a non-zero size at the stable timestamp when we enter rollback. To fix this, we can clear the "needing size adjustment" set at the beginning of replication rollback.

        Attachments

          Issue Links

          is related to

          Task - A task that needs to be done. SERVER-33488 WT SizeStorer dislikes RTT

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

          Task - A task that needs to be done. SERVER-33863 Add transactions and ddl operations on transactions table to rollback fuzzer

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34977 subtract capped deletes from fastcount during replication recovery

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35435 Renaming during replication recovery incorrectly allows size adjustments

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-42312 Validate during rollback can cause count mismatch

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

          Task - A task that needs to be done. SERVER-35052 Turn off fastcount checks on capped collections in rollback fuzzer

          • 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:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: