Invalidate default read write concern cache on replication rollback

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Sharding 2020-01-13, Sharding 2020-01-27
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After a rollback (to a timestamp or via refetch), the default read write concern cache should be invalidated.

            Assignee:
            Jack Mulrow
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: