[SERVER-16683] Decrease mongos memory footprint when shards have several tags Created: 29/Dec/14 Updated: 19/Jun/15 Resolved: 07/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.8.0-rc4 |
| Fix Version/s: | 2.6.7, 2.8.0-rc5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Completed: | |||||||||
| Participants: | |||||||||
| Description |
|
Currently, each Chunk object has its own copy of a Shard instance, and the Shard object contains all the tags for the shard. This can cause an explosion in memory usage when the cluster contains many chunks. |
| Comments |
| Comment by Randolph Tan [ 07/Jan/15 ] |
|
The summary of the change made here is the removal of _tags member variable from the Shard class. A new method is created just for extracting the tags information from the config server during balancing and top chunk migration during auto-split to replace the old one that was relying on Shard class containing the _tags. |
| Comment by Githook User [ 06/Jan/15 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |
| Comment by Githook User [ 06/Jan/15 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |