[SERVER-4242] geShardDistribution in 2.0.2 Created: 10/Nov/11 Updated: 11/Jul/16 Resolved: 16/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | 2.0.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Backport coll.getShardDistribution() and coll.getSplitKeysForChunks() into 2.0.2. Makes getting a snapshot of chunk stats much easier / calculates split points and creates safe splitting function for incorrectly split chunks for any chunk size. 10ab1ed6 and then df07b8f5 |
| Comments |
| Comment by Greg Studer [ 10/Nov/11 ] |
|
@scott - Actually read "utils_sh.js" as "utils for shell" The function reports information on just that collection though : could rename like db.stats(), coll.stats() -> coll.shardStats() (and put the coll itself in utils_sh.js). getSplitKeysForChunks() can probably also go there, makes more sense as a utility. |
| Comment by auto [ 10/Nov/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: |
| Comment by Greg Studer [ 10/Nov/11 ] |
|
Backporting but marking _getSplitKeysForChunks() as hidden, as it has been only lightly tested. |
| Comment by Scott Hernandez (Inactive) [ 10/Nov/11 ] |
|
Shouldn't these be "sh" (sharding) functions, and not on the collection? |