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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Blocked
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              milkie Eric Milkie
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated: