[SERVER-4365] handle network partitions between client and mongod primary Created: 23/Nov/11  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Greg Studer Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: RachitaD
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-4377 handle most network partitions betwee... Closed
Assigned Teams:
Cluster Scalability
Participants:

 Description   

This is a case in which replica set failover doesn't work well - this would eliminate a single point of network failure.



 Comments   
Comment by Greg Studer [ 28/Nov/11 ]

As per our discussion, one option is adding arbiters to all clients.

Maybe modify voting such that client arbiters can only vote to change the priority of replica set members, but don't actually vote in elections.

Comment by Scott Hernandez (Inactive) [ 27/Nov/11 ]

How many clients and which ones should be considered good enough to affect elections? This seems like a big issue if the client pool is dynamic.

Comment by Greg Studer [ 23/Nov/11 ]

... potentially via stepdown messages from smart clients?

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