Investigate and remove unnecessary causalConsistency=false settings in sharding testing

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Sharding
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, a fair amount of our testing, especially transactions testing, uses sessions with causalConsistency explicitly set to false (as opposed to using the default). Per a discussion with judah.schvimer, this setting is left over from early transactions testing, and is not necessarily required for new tests.

              Assignee:
              [DO NOT USE] Backlog - Sharding Team
              Reporter:
              Maria van Keulen
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: