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

Secondary in rollback_after_enabling_majority_reads.js goes into rollback before validate command

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.6, 4.0.19, 4.7.0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2, v4.0
    • Sprint:
      Repl 2020-03-23, Repl 2020-04-06, Repl 2020-04-20
    • Linked BF Score:
      5

      Description

      In rollback_after_enabling_majority_reads.js, we first verify that we fassert if we do a rollback immediately after upgrading enableMajorityReadConcern to true. Then, we restart the node and verify that it reaches SECONDARY state. However, after we verify that the node has fully restarted, it seems possible for the node to go into ROLLBACK (if, for instance, the source's last oplog entry was early than our first oplog entry). This would cause the verify command on the next line to fail.

        Attachments

          Activity

            People

            Assignee:
            xuerui.fa Xuerui Fa
            Reporter:
            xuerui.fa Xuerui Fa
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: