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

Investigate replica set data mismatch from Jepsen testing

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Fully Compatible
    • Execution Team 2020-06-29
    • 91

      Our internal testing of MongoDB 4.4 using the Jepsen testing methodology is reporting that different members of a replica set have different data at the end of a test.

      The issue appeared to start with this drop of WiredTiger - though the failure is sporadic, so that's not a strong indicator that a bug was introduced in that set of changes.

      The Jepsen test simulates different failure modes in a distributed system - so it's possible that this failure is related to recovery, rollback to stable or replication rollback via refetch.

      We should dig into the failure, and try to find a way to isolate the root cause.

        1. wt-6411-repro.diff
          4 kB
          William Schultz

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: