Session Migration keeps original oplog wall time when creating new no-op entries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This causes it to insert oplog entries with older wall time. lastAppliedWallTime stat appear to derive the value from the oplog and this can cause it to go back in time.

            Assignee:
            Unassigned
            Reporter:
            Randolph Tan
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: