[SERVER-36958] Parts of the `_configsvrShardCollection` command do not retry on network errors Created: 31/Aug/18  Updated: 29/Oct/23  Resolved: 30/Jan/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.0.2, 4.1.2
Fix Version/s: 4.0.7, 4.1.8

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Esha Maharishi (Inactive)
Resolution: Fixed Votes: 0
Labels: ShardingRoughEdges, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Sharding 2018-12-17, Sharding 2018-12-31, Sharding 2019-01-14, Sharding 2019-01-28, Sharding 2019-02-11
Participants:
Linked BF Score: 34

 Description   

Parts of the _configsvrShardCollection command implementation still use ScopedDbConnection for the validation logic. Because of this it does not retry on shard network errors.

With the introduction of its _shardsvrShardCollection counterpart, this validation code can completely be pushed into the shard command, which will solve this problem.



 Comments   
Comment by Githook User [ 07/Feb/19 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-36958 Parts of the command do not retry on network errors
Branch: v4.0
https://github.com/mongodb/mongo/commit/09d236a3a13e0355f884b3b04297c888f6fa53c4

Comment by Githook User [ 30/Jan/19 ]

Author:

{'username': 'Kimchelly', 'email': 'kimberly.tao@mongodb.com', 'name': 'Kim Tao'}

Message: SERVER-36958: allow _configsvrShardCollection to retry on network errors
Branch: master
https://github.com/mongodb/mongo/commit/2b4514bdf69eecee3e90bb4ccfa6cba7e5f09a8a

Comment by Gregory McKeon (Inactive) [ 30/Nov/18 ]

kaloian.manassiev is this committed?

Comment by Githook User [ 05/Sep/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-36958 Make sharding_multiple_ns.js wait for the CSRS primary to discover downed shard node

(cherry picked from commit 39355c3221284c4b2cff3ebd89c86c0316d5380e)
Branch: v4.0
https://github.com/mongodb/mongo/commit/5d8c3fcc095c20be7542078fd1139bf9c00254f2

Comment by Githook User [ 05/Sep/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-36958 Make sharding_multiple_ns.js wait for the CSRS primary to discover downed shard node
Branch: master
https://github.com/mongodb/mongo/commit/39355c3221284c4b2cff3ebd89c86c0316d5380e

Comment by Kaloian Manassiev [ 31/Aug/18 ]

In the mean time, in sharding_multiple_ns.js, the code waits for mongos to discover the stopped, but the command actually executes on the config server primary, so we need to add a workaround in order to prevent the test from failing.

Generated at Thu Feb 08 04:44:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.