[SERVER-4429] When moving primary need to inform all other mongoses Created: 05/Dec/11  Updated: 05/Dec/11  Resolved: 05/Dec/11

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

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File mongos_move_primary_weirdness.js    
Issue Links:
Related
related to SERVER-4262 when dropping collections need to inv... Closed
Operating System: ALL
Participants:

 Description   

The new shard for a database on movePrimary is not propagated to mongos automatically - this should trigger a StaleConfigException on a sharded connection.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 05/Dec/11 ]

SERVER-3413

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