[SERVER-4223] Add better retry logic to mongos on doing updates to config data Created: 07/Nov/11  Updated: 06/Dec/22  Resolved: 24/Aug/16

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

Turn off balancing
Bring down one config server
Bring that config server back up
Then try to turn balancing back on. The write to the config database will fail with a transport error indicating the mongos can't reach the config server that was just down. If you try the same write again, however, the write goes through b/c the mongos has reconnected with the config server. There should be retry logic in the mongos to handle this so that the mongos will automatically reconnect to the newly restarted config server and try the update again.



 Comments   
Comment by Spencer Brody (Inactive) [ 24/Aug/16 ]

Now that config servers are a replica set the system is much more resilient to config servers transiently going down.

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