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

Removing replica set node can cause mongos to use already freed _nodes entry

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.0.3
    • Component/s: Sharding, Stability
    • Labels:
      None
    • ALL

      If the primary is the last element in the _nodes array a node is removed from the replica set, it is possible to call _checkConnection on the primary such that a node is removed from the _nodes array but then _master is set to the master's old index in the _nodes array, which now points to freed memory.

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

              Created:
              Updated:
              Resolved: