Some reads work while system is RECOVERING

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v4.2, v4.0, v3.6
    • 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"}
    • Repl 2020-02-10, Repl 2020-02-24
    • 32
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Vesselina Ratcheva (Inactive)
            Reporter:
            Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: