[SERVER-20221] Remove unsetSharding call from dropCollection Created: 31/Aug/15  Updated: 06/Dec/19  Resolved: 06/Dec/19

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

Type: Task Priority: Minor - P4
Reporter: Spencer Brody (Inactive) Assignee: Haley Connelly
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-12-16
Participants:

 Description   

The unsetSharding command removes a connection's associated shardVersions.

As part of dropCollection, the config server sends unsetSharding to all shards over the TaskExecutor/NetworkInterface networking stack, but all commands run through the TaskExecutor that need versioning information attach that information to the command being run directly, rather than setting it on the connection via the setShardVersion command. So, this unsetSharding command is a no-op, and can be removed.



 Comments   
Comment by Githook User [ 06/Dec/19 ]

Author:

{'name': 'Haley Connelly', 'username': 'haleyConnelly', 'email': 'haley.connelly@10gen.com'}

Message: SERVER-20221 Remove unsetSharding call from dropCollection
Branch: master
https://github.com/mongodb/mongo/commit/244e66368d9eb8a0c5425b5b8abd3a4138a897fa

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