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

RID is not a sufficiently unique identifier

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

      create 3 node replset on a single machine
      shut down a secondary
      copy the other secondary's data files onto that secondary's data directory
      restart that secondary
      observe that w:3 write concerns can no longer be satisfied

      Show
      create 3 node replset on a single machine shut down a secondary copy the other secondary's data files onto that secondary's data directory restart that secondary observe that w:3 write concerns can no longer be satisfied

      RIDs can overlap, masking one node's replication progress and failing to correctly report write concern (under counting the number of nodes who have received the write).

      RIDs can be replaced when not entirely necessary. If a node changes its hostname, it will choose a new RID. This can result in its replication progress being reported to the primary as two different nodes, resulting in falsely satisfied write concerns.

      Current proposal: use a combination of config version and _id from that config to uniquely identify nodes instead

            Assignee:
            matt.dannenberg Matt Dannenberg
            Reporter:
            matt.dannenberg Matt Dannenberg
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: