[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:
Related
Tested
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: SERVER-16683 Decrease mongos memory footprint when shards have several tags
Branch: v2.6
https://github.com/mongodb/mongo/commit/293bf1caf51df5b9cf7c882f2e6312769e1716a2

Comment by Githook User [ 06/Jan/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-16683 Decrease mongos memory footprint when shards have several tags
Branch: master
https://github.com/mongodb/mongo/commit/9080534036974a91067cef0ace3aff60c65a123b

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