[SERVER-29232] replace use of ScopedDbConnection in shardCollection with a TaskExecutor::scheduleRemoteCommand derivative Created: 16/May/17  Updated: 08/Jun/17  Resolved: 08/Jun/17

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-29107 move shardCollection logic into new _... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-05-29, Sharding 2017-06-19
Participants:

 Description   

This is to support internal auth within a sharded cluster when shardCollection is moved to the config server.

Internal auth is done through the ShardingConnectionHook for connections from DBConnectionPool (where ScopedDbConnection gets its connection).

However, the ShardingConnectionHook is not added to the DBConnectionPools on config servers (it gets added to globalConnPool and shardConnectionPool on mongod on sharding initialization from a shardIdentity, which doesn't happen on config servers).



 Comments   
Comment by Esha Maharishi (Inactive) [ 08/Jun/17 ]

Marking as a dupe of SERVER-29107, since this was solved in that ticket by adding ShardingConnectionHook to the DBConnectionPools on config servers.

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