[SERVER-18464] Move per-shard connection management to Shard Created: 13/May/15  Updated: 11/Nov/15  Resolved: 17/Jun/15

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 3 05/15/15, Sharding 4 06/05/15, Sharding 5 06/26/16
Participants:

 Description   

With the RemoteCommandTargeter being under Shard, it is prudent to also move the connection pooling to be per-shard as well.

This also means that different entities within mongos should not cache references to Shard, but use identifiers and look up shards from the shard registry.



 Comments   
Comment by Githook User [ 17/Jun/15 ]

Author:

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

Message: SERVER-18464/SERVER-18437/SERVER-19004 Move targeter ownership to Shard

Currently there is a discrepancy between the ownership of the targeter
object and the lifetime of Shard. It is possible that if a shard has been
created and a targeter disappears then operations on that shard will not
find the targeter.

This change moves the ownership of targeter to the Shard object itself.
Branch: master
https://github.com/mongodb/mongo/commit/6584bfd3ddcdb1598fb486615c49f0272798f5d6

Comment by Githook User [ 11/Jun/15 ]

Author:

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

Message: SERVER-18464 Implement ReplicaSetMonitorManager to replace statics

The ReplicaSetMonitorManager will be responsible for the lifetime of
replica set monitors and will replaces the global static variables, which
we currently use to track the replica set monitors.

This change brings us closer to having a separate instance of the replica
set monitors for MongoS.
Branch: master
https://github.com/mongodb/mongo/commit/7c028e4f68c73d4e598b4836051678d307fa8adb

Comment by Githook User [ 10/Jun/15 ]

Author:

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

Message: SERVER-18464 Cleanup unused code and tests from Shard

Now that shard is no longer copyable these tests and code are no longer
relevant.
Branch: master
https://github.com/mongodb/mongo/commit/5f909dc865fe096f34bd85442ec89c722e864c1a

Comment by Githook User [ 14/May/15 ]

Author:

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

Message: SERVER-18464 AuthZ manager reads should use the config shard

Change the Authorization Manager's read code to obtain connection using
the config shard directly. We never access other shards from there so no
need to go through the config database metadata.
Branch: master
https://github.com/mongodb/mongo/commit/c03365803d286ee0382b5fd3447140e7017c07cc

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