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

Use non-snapshot read concern for sharded transaction in aggregation_currentop.js

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Sprint:
      Sharding 2019-10-07
    • Linked BF Score:
      35

      Description

      To test the $currentOp output for sharded transactions, sharding/aggregation_currentop.js starts a transaction through mongos using "snapshot" read concern, which can occasionally with SnapshotTooOld, which mongos can't retry on until SERVER-39704 is completed. The test doesn't rely on the particular read concern level of this transaction, so to avoid this problem the transaction can use a read concern level that does not require a global snapshot - majority, local, or none.

        Attachments

          Activity

            People

            Assignee:
            alex.taskov Alexander Taskov
            Reporter:
            jack.mulrow Jack Mulrow
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: