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

Secondary position information can be erroneous if nodes leave and rejoin a cluster with less data than before

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Replication
    • ALL

      For example, say a node with member id 2 in the config crashes. The data is restored from backup taken a day prior and restarted. Now the node begins reporting upstream for id 2 a position that is behind where id 2 had previously reported.
      Today's position managing code does not change a node's position if it is reported to have moved backward.

      This is a problem because nodes can thus appear to contain data that they do not actually have.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: