Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Sharding, Testing Infrastructure
Labels:
None

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

Potentially could use the existing "throwSockExcep" failpoint.

One important test here is that a sharded system can recover after a RS failover triggered by the primary of the replSet losing network connecitivity.

is depended on by

SERVER-4661 Mongos doesn't detect primary change if old primary lost network connectivity

Closed

is duplicated by

SERVER-5642 Make mongobridge work with ShardingTest to facilitate testing network partitions in a sharded system

Closed

SERVER-20982 Add concurrency workload framework to triggers various node failovers

Closed

related to

SERVER-4706 when a socket between mongos and mongod fails, close all connections immediately

Closed

Assignee:: Unassigned
Reporter:: Spencer Brody (Inactive)
Participants:: auto, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Nov 07 2012 12:35:57 AM UTC
Updated:: Oct 19 2015 03:56:41 PM UTC
Resolved:: Oct 19 2015 02:17:19 PM UTC
Confidence Status Last Update:: 15/Mar/13 4:13 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates