Read committed violation

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • Sharding NYC 2023-05-01, Sharding NYC 2023-05-15, Sharding NYC 2023-05-29, Sharding NYC 2023-06-12
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We found one consistency violation issue about not read committed. Here is the Jepsen log:  https://github.com/jerrytesting/mongodb-read-committed-violation and hope it could help figure out the root cause. 

            Assignee:
            Max Hirschhorn
            Reporter:
            jerry testing
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: