Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-29232

replace use of ScopedDbConnection in shardCollection with a TaskExecutor::scheduleRemoteCommand derivative

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.5.7
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-05-29, Sharding 2017-06-19

      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).

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: