afterClusterTime reads should not block on prepare conflicts if their afterClusterTime is before the oldest prepare timestamp

XMLWordPrintableJSON

    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After SERVER-36382, all afterClusterTime reads block on prepare conflicts.

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Samyukta Lanka
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: