[SERVER-5166] Removing replica set node can cause mongos to use already freed _nodes entry Created: 01/Mar/12  Updated: 15/Aug/12  Resolved: 03/Apr/12

Status: Closed
Project: Core Server
Component/s: Sharding, Stability
Affects Version/s: 2.0.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Randolph Tan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-5110 ReplicaSetMonitor::check not thread s... Closed
Related
Operating System: ALL
Participants:

 Description   

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.


Generated at Thu Feb 08 03:08:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.