[SERVER-9645] Have Mongos handle connection exceptions to shards internally Created: 10/May/13  Updated: 06/Dec/22  Resolved: 12/Jul/18

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

Type: Bug Priority: Major - P3
Reporter: David Hows Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Currently if there is a connection exception when running a query on a MongoS the connection exception will be returned to the client as the query failed.

We should look at having these exceptions handled internally and if possible retry the query.



 Comments   
Comment by Gregory McKeon (Inactive) [ 12/Jul/18 ]

With retryable writes and auto-retry logic in the drivers and mongos, this has gone away.

Comment by David Hows [ 10/May/13 ]

Steps to reproduce.

  1. Create cluster with 3 shards
  2. Insert 3 documents via mongo shell
  3. Split & move documents over shards, 1 doc per shard
  4. Query all documents
  5. Shutdown a shard
  6. query all documents - connection exception here
  7. Subsequent queries will not show the connection exception
Generated at Thu Feb 08 03:21:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.