-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.0.6, 2.1.2
-
Component/s: None
-
ALL
There is no check for the nodesOffset variable inside checkConnection. This can cause race condition that can potentially result in accessing the _nodes outside of its bounds. The problem can potentially manifest when whenever members of a replica set shrinks in size.
- duplicates
-
SERVER-6508 Resizing of _nodes and updating _master is not atomic in ReplicaSetMonitor
- Closed
- is duplicated by
-
SERVER-6798 moveChunk Invalid access at address Segmentation Fault
- Closed
- is related to
-
SERVER-6583 "couldn't connect to new shard socket exception" in addshard4.js
- Closed
- related to
-
SERVER-6548 Unsafe use of _master in ReplicaSetMonitor::_check() and ReplicaSetMonitor::check() can lead to segfault
- Closed
-
SERVER-6647 Potential out of bounds access in ReplicaSetMonitor
- Closed
-
SERVER-5058 mongos should update config seed based on rs version
- Closed