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

read_operations_during_rollback.js should make sure that 'GetMoreHangBeforeReadLock' failpoint is hit on correct collection

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.7.0
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2020-05-04

    Description

      The read_operations_during_rollback.js test waits for us to hit a GetMoreHangBeforeReadLock failpoint here. It is possible this failpoint is triggered on a collection we don't expect (e.g. local.oplog.rs), causing us to continue erroneously, before this getMore command is hung. This causes this getMore to succeed, because we ended up starting the rollback before the getMore had started. We should make sure that the getMore command is hung on the right collection before proceeding.

      Attachments

        Activity

          People

            william.schultz@mongodb.com William Schultz (Inactive)
            william.schultz@mongodb.com William Schultz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: