rollback_via_refetch_anomaly.js fails on inMemory storage engine

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.21
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • 38
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Observed in the 4.0 branch:

      assert.soon failed, msg : Could not find log entries containing the following message: We cannot transition to SECONDARY state because our 'lastApplied' optime is less than the initial data timestamp and enableMajorityReadConcern = false
contains@src/mongo/shell/check_log.js:58:1
@jstests/replsets/rollback_via_refetch_anomaly.js:168:1

            Assignee:
            A. Jesse Jiryu Davis
            Reporter:
            A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: