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

Blacklist rollback_after_enabling_majority_reads.js from multiversion suite

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.3
    • None
    • Replication
    • None
    • Fully Compatible
    • Repl 2020-01-13
    • 50

    Description

      If a node was primary in 4.3 but restarted with a 4.2 binary after an unclean shutdown. The fastcount of oplogTruncateAfterPoint could be wrong. This is related to SERVER-41391 where we added a function to correct the fastcount. But since 4.2 doesnt have that ability (unless we backport that), restarting a node with a 4.2 binary after an unclean shutdown in 4.3, the fastcount could be wrong.

      We do not even support a crashed v4.3 binary being restarted with a v4.2 binary. So putting the requires_fcv_44 tag to the test.

      Attachments

        Activity

          People

            lingzhi.deng@mongodb.com Lingzhi Deng
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: