[SERVER-17848] Use the catalog manager to query shards in a sharded cluster Created: 01/Apr/15  Updated: 19/Sep/15  Resolved: 13/Apr/15

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

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2 04/24/15
Participants:

 Description   

In some places in src/mongo/s, we directly query the config server for the shards, we should use the catalog manager instead.
For example,

 ScopedDbConnection conn(configServer.getPrimary().getConnString(), 30);
auto_ptr<DBClientCursor> cursor(conn->query(ShardType::ConfigNS , Query()));

in balancer_policy.cpp



 Comments   
Comment by Githook User [ 13/Apr/15 ]

Author:

{u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}

Message: SERVER-17848 Use the catalog manager to query shards in a sharded cluster
Branch: master
https://github.com/mongodb/mongo/commit/24a6a5cc8201b6cd62b4365fee6d1d0a018f5545

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