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

TransactionHistoryIterator should always do untimestamped reads

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.0-rc1, 4.3.1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Repl 2019-06-17
    • 12

      SERVER-41178 fixed the timestamp read issue in rollback recovery, but doing timestamp read with unset last applied may also make oplog writes invisible in initial sync.

            Assignee:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: