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

Check whether or not to read from the last applied timestamp before accessing the value

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.5
    • Affects Version/s: 3.7.4
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-04-23
    • 33

      A BF is caused by calling ReplicationCoordinator::getMyLastAppliedOpTime() before checking if we should. On embedded, which hits a MONGO_UNREACHABLE.

      We should change the logic to check whether or not to read the timestamp before accessing it.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: