[SERVER-28098] Get rid of DBConfig::getAllShardIds Created: 24/Feb/17 Updated: 05/Apr/17 Resolved: 24/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.3 |
| Fix Version/s: | 3.4.3, 3.5.4 |
| 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 | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Sprint: | Sharding 2017-03-06 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The DBConfig::getAllShardIds method returns all shards on which collections from a particular database have chunks, plus the primary shard. It is only used by map/reduce with sharded output in order to provide a set of shards on which to spread the output collection. Instead of using this methodology we should just use all available shards. |
| Comments |
| Comment by Githook User [ 01/Mar/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: (cherry picked from commit 5c182c1d5e8a141e6dcd156173f802f4e44b3610) |
| Comment by Kaloian Manassiev [ 24/Feb/17 ] |
|
As part of this change, the map/reduce sharded output collection will now be spread potentially across all available shards instead of only going to those shards which have chunks associated with collection on the owning the database. |
| Comment by Githook User [ 24/Feb/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |