Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.0.7, 2.2.0-rc1
Affects Version/s: 2.0.6, 2.1.2
Component/s: None
Labels:
- replication

Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

(1 related to)

Assignee:: Randolph Tan
Reporter:: Randolph Tan
Participants:: auto, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 18 2012 08:01:44 PM UTC
Updated:: Jul 11 2016 05:57:07 PM UTC
Resolved:: Jul 26 2012 03:17:32 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates