Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 2.0.2, 2.2.0-rc0
Component/s: Replication
Labels:
- elections
Environment:
Ubuntu 10.04.3 LTS

Operating System:
Linux
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

cluster of 3 nodes and clients connected through mongos
from primary issue rs.remove("secondary1")
found application lost connection and threw error lost connection to primary node.

This consistently happens even when the cluster is 4-node or 5-node.

duplicates

SERVER-5788 primary stepdown on reconfig isn't needed in some cases

Closed

is duplicated by

SERVER-9717 Remove unnecessary voting after replica set config change

Closed

related to

SERVER-5286 DBClientBase::findN: transport error for query: { mapreduce.shardedfinish: {....} }

Closed

SERVER-4315 Make sure replica set primary does not disconnect unnecessarily on reconfig

Closed

SERVER-6376 Tag replica set nodes without election or reconnections

Closed

Assignee:: Unassigned
Reporter:: Gopi
Participants:: Daniel Pasette, Gopi, Juho Mäkinen, Spencer Brody
Votes:: 3 Vote for this issue
Watchers:: 12 Start watching this issue

Created:: Aug 10 2012 09:33:47 PM UTC
Updated:: Aug 14 2014 03:00:39 PM UTC
Resolved:: Aug 14 2014 03:00:39 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates