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

rollback_via_refetch_anomaly.js fails on inMemory storage engine

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.21
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Linked BF Score:
      38

      Description

      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

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: