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

Wait for 2-phase drop to finish in transaction tests

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Replication
    • None
    • Replication

    Description

      Collection 2-phase drop needs the DB lock in X mode which will block or abort the transactions, so we need to wait for them to be majority committed in SERVER-34349. However, this is not sufficient since the reaper runs asynchronously afterwards. We don't follow SERVER-34372 to complicate the logic of waiting for write concern. Instead, we will fix the tests for now and eventually with storage engine support, we don't have to acquire the DB lock in X mode to drop drop-pending collections.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34349 Wait for drop to be majority committed in transaction tests

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

          Task - A task that needs to be done. SERVER-34069 Postpone 2nd phase of collection drop until drop timestamp is in the stable checkpoint

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-34372 Drop collection command with majority write concern should wait until two-phase drop finishes

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

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              siyuan.zhou@mongodb.com Siyuan Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: