Initial sync should not timestamp secondary indexes at the current 'clusterTime'

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Repl 2018-05-07
    • 50
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      During initial sync, a secondary will timestamp an index build at the clusterTime, which may occur after the lastAppliedOpTime. The lastAppliedOpTime is used to indicate the latest a reader is allowed to read. If secondary reads are allowed during batch application, a reader will wait for future catalog changes that may never come. The current workaround is to retry the read while taking the PBWM lock, which is suboptimal.

            Assignee:
            Daniel Gottlieb (Inactive)
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: