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

Consider removing comparison operators from OpTime class

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Repl 2017-03-27, Repl 2017-04-17, Repl 2017-05-08

      Comparing OpTimes from different terms is fundamentally problematic as they could be from different branches of history. Every time we compare two optimes without checking that they come from the same term is suspicious. We at least need to audit all places where do do optime comparisons, and we should consider removing the optime comparison operators entirely so all places that compare optimes must think about term differences explicitly.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: