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

Some reads work while system is RECOVERING

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.4, 4.0.20, 3.6.19, 4.2.9
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2, v4.0, v3.6
    • Steps To Reproduce:
      Hide

      A mongod can be forced to stay in RECOVERING by setting the rsSyncApplyStop failpoint.

      --setParameter enableTestCommands=1 --setParameter 'failpoint.rsSyncApplyStop=

      {"mode": "alwaysOn"}
      Show
      A mongod can be forced to stay in RECOVERING by setting the rsSyncApplyStop failpoint. --setParameter enableTestCommands=1 --setParameter 'failpoint.rsSyncApplyStop= {"mode": "alwaysOn"}
    • Sprint:
      Repl 2020-02-10, Repl 2020-02-24
    • Case:
    • Linked BF Score:
      32

      Description

      While the replication system is in RECOVERING, we cannot read collection data (error code NotMasterOrSecondary). However, provided we have allowed secondary reads, we CAN do a listDatabases or listCollections or listIndexes. This seems bad, since the results of these reads may represent database states which are inconsistent or at a point in time prior to a previously reported lastDurable time of the node.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              vesselina.ratcheva Vesselina Ratcheva
              Reporter:
              matthew.russotto Matthew Russotto
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: