snapshot_read_kill_operations.js should consider Interrupted as an acceptable getMore error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor - P4
    • 4.0.0-rc5, 4.1.1
    • Affects Version/s: None
    • Component/s: Storage
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2018-06-18
    • 11
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The killOp phase of the snapshot_read_kill_operations.js workload targets any running getMore, not only one started by that thread. This means that it is possible for any thread's snapshot getMore to get killed while it is running, leading to a getMore returning an "operation was interrupted" error message. Presumably, we do want to test snapshot getMore operations getting concurrently killed, but we don't want the test to fail in this case. We should likely add a new acceptable error (Interrupted) to the doSnapshotGetMore call, so that the test does not fail in this case.

            Assignee:
            Audrey Fang (Inactive)
            Reporter:
            Will Schultz
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: